This is the Azure SDK parent repository and mostly contains documentation around guidelines and policies as well as the releases for the various languages supported by the Azure SDK.
Перейти к файлу
Adrian Hall 8c239e1888
Moved design guidelines and links to the repos to a table (#372)
2019-05-20 08:55:47 -07:00
.azure-pipelines Updates for standardization (#131) 2019-01-30 17:49:07 -08:00
.github Updating tags and CODEOWNERS (#366) 2019-05-14 13:43:23 -07:00
.vscode Add watch task and vscode config with recommended extensions (#167) 2019-02-06 14:43:29 -08:00
docs [General] Configuration guidelines (#328) 2019-05-15 18:11:17 -07:00
.gitignore Fixing css after typescript merge, and removing generated output. (#128) 2019-01-31 13:29:16 +13:00
LICENSE Initial commit 2018-11-08 14:03:45 -08:00
README.md Moved design guidelines and links to the repos to a table (#372) 2019-05-20 08:55:47 -07:00
package.json Add watch task and vscode config with recommended extensions (#167) 2019-02-06 14:43:29 -08:00

README.md

Azure SDK

The Azure SDK delivers a platform for developers to leverage the wide variety of Azure services in their language of choice. The source for the client libraries exists for the most part in repositories for each language. This repository is meant to be a jumping off point into those language specific repositories. Issues related to a specific language should be opened in the corresponding repository but cross cutting issues can be opened in this repository.

Language Guidelines Repo
C# /.NET Link azure-sdk-for-net
Java Link azure-sdk-for-java
JavaScript Link azure-sdk-for-js
Python Link azure-sdk-for-python
Go azure-sdk-for-go

Service teams should schedule reviews of their client libraries with the ADP Review Board. See the Review Process for more information.

Terminology

  • SDK: Software Development Kit. This refers to the entire Azure SDK for a single language, itself broken up into numerous Azure SDK Client Libraries (as defined below).

  • Client Library. This refers to a library (and associated tools, documentation, and samples) that customers/developers use to ease working with an Azure service. There is often one client library per service and per programming language. Sometimes a single client library will contain the ability to connect to multiple services. Each client library is published separately to the appropriate language-specific package repository. These releases are performed exclusively by the Azure SDK engineering systems team. Customers/Developers consume and use each client library separately as necessary to solve their use case.

  • Package. This refers to a client library after it has been packaged for distribution for customer-developers to consume. Examples are:

    • A Nuget package for a .NET client library
    • A Maven package for a Java library
    • An NPM package for a JavaScript library
    • A Python wheel for a Python library

Azure Service Libraries

The following is a list of Azure services and links to their open source code:

Client Libraries

Service Name .NET Java Python JavaScript Go
Azure Storage code code code code code
CosmosDB code code code
Key Vault code code code code
Service Bus code code code code
Event Hubs code code code code
IotHub, Iot Devices, IotHub Provisioning Service, IotHub Provisioning Device code code code code
Event Grid code code code code
Batch code code code code
HDInsight code code code code code
Notification Hubs
Application Insights Ingestion code code code code
Application Insights Query code code code code
Log Analytics Ingestion
Log Analytics Query code code code code
Service Fabric
Data Lake Analytics code code code code
Data Lake Store code code code
Azure Search code
Relay code code
Cognitive Services code code code code
SQL
MySQL
PostgreSQL
Redis

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Internal azure-sdk DevOps Wiki