Read on Twitter
Introducing the new #Azure SDKs
A 3 minute video that brings you through our motivation for creating the new SDKs - it's all centered around increasing developer productivity while building Azure solutions.
https://aka.ms/azsdk
(1/14)
A 3 minute video that brings you through our motivation for creating the new SDKs - it's all centered around increasing developer productivity while building Azure solutions.
https://aka.ms/azsdk
(1/14)
Before we introduced the new Azure SDKs in July of 2019, each Azure Service team independently created their own SDKs in disparate repositories, had their own CI process, and had varying levels of authentication, language, OS, and package support.
(2/14)
(2/14)
With the new Azure SDKs we have established a set of common design guidelines, a centralized engineering system, centralized OSS repositories, consistent authentication, language, and OS support. We also deliver packages to the most popular package managers for each lang.
(3/14)
(3/14)
We currently provide libraries in #DotNet, #Java, #Python, and #JavaScript/ #TypeScript with more languages coming soon. https://aka.ms/azsdk will lead you to our website, which a great landing spot with links to our packages, guidelines, documentation, and blog.
(4/14)
(4/14)
Developer productivity is the primary driver for the new Azure SDK effort.
We know that you will be most productive when your experience feels natural for whatever lang you code in and when you can easily download the libs from package managers that you use every day.
(5/14)
We know that you will be most productive when your experience feels natural for whatever lang you code in and when you can easily download the libs from package managers that you use every day.
(5/14)
Consistency is also key, with the new Azure SDKs, navigating amongst the services doesn’t require you to learn a new API paradigm.
(6/14)
(6/14)
Being approachable, diagnosable, and dependable are pillars that go into building libraries, so we are investing heavily in these areas. We are ramping up our doc efforts, integrating with standard OSS frameworks, and holding API board reviews for all new libraries.
(7/14)
(7/14)
You can find our guidelines at https://aka.ms/azsdk/guide . We’ll continue to evolve these guidelines, so please review them, and provide us with feedback or suggestions via GitHub. We released our first GA libraries in the fall of 2019 and continue to release monthly.
(8/14)
(8/14)
In GA, we currently have Storage, Key Vault, Event Hubs, App Config, Cosmos, Cognitive Search, Cognitive Services Text Analytics. Azure.Identity and Azure.Core which implement a consistent authentication and request/response pipeline for all libraries.
(9/14)
(9/14)
In Preview, we have Cosmos for .NET, Cognitive Services Form Recognizer, Service Bus, and the Azure SDK for Embedded C
We’ll eventually GA libraries for all Azure services, but next up on the list is Tables, Event Grid, and the new Resource Management libs.
(10/14)
We’ll eventually GA libraries for all Azure services, but next up on the list is Tables, Event Grid, and the new Resource Management libs.
(10/14)
You can find the full list of libraries with links to packages, code, and docs at https://aka.ms/azsdk/releases .
(11/14)
(11/14)
Links to our repos can be found in our central repo https://aka.ms/azsdk/github which has links to all the other language specific repos and houses our common design guidelines. It's a great place to file suggestions, questions, or issues that cut across all langs.
(12/14)
(12/14)
The overriding theme here is everything in the open on GitHub, with an engaged engineering team to help you through any issues you discover as you build your Azure solutions.
(13/14)
(13/14)
We’d like to encourage you to start using the new Azure SDKs and contributing to them by submitting issues or pull-requests on GitHub. You can follow us on Twitter https://twitter.com/AzureSDK and subscribe to our blog at https://aka.ms/azsdk/blog .
(14/14)
(14/14)
