Build 2017 - P4034 - Agile app development with Azure API Management
Download as pptx, pdf2 likes314 views
The document discusses Azure API Management, focusing on the integration of mobile analytics, IoT, and microservices with third-party APIs. It highlights the importance of managing API changes through developer portals, versioning strategies, and the capabilities of the platform as of May 2014, including its extensive customer base and usage statistics. Azure API Management supports a diverse range of industries with significant monthly API calls across multiple regions.
Build 2017 - P4034 - Agile app development with Azure API Management
- 3. APIs outside Azure 3rd party APIs AZURE API MANAGEMENT APIs on Azure Azure APIs
- 4. APP DEVELOPERS APPS API MANAGERS Hosted anywhere Developed using any technology BACKEND APIs DIRECT VPN ExpressRoute Admin portal Gateway Developer Portal
- 5. HTTP APIs are different
- 9. API Contract
- 12. API Management Versions and Revisions
- 14. Managing Change with API Management Developer portal for advertising change OpenAPI Contract Gateway façade for hiding changes Versions and Revisions for temporal control
- 15. May 2014 Launched on Azure 7.7K Customers 21% of Fortune 100 Banking, insurance, energy, retail, transportation, manufacturing… 29K Total APIs 20B Total calls per month 27 Regions in 14 geos 250M Calls per day by the top customer
Editor's Notes
- #2: Work on the Azure API management team This talk -> using API Management to build Agile Apps To be agile means to embrace incremental change We are going to talk about managing change in HTTP Apis But before we do…
- #3: API economy makes APIs a first class concept Not just an implementation detail that only devs care about It is a contract between providers and consumer API maybe just a supporting function Driving mobile app, or 3rd party integration Or actually a product in itself Critical part of the business service
- #4: So how can Azure API management help… … Now you have and idea what it can do, let’s look at architecture
- #5: Three components: dev portal, gateway, admin portal … Backend hosted anywhere on any platform, As long as it is a HTTP API
- #6: HTTP APIs are different … In order to clear make this distinction, Introduce new language
- #7: Terms usually used interchangeably … Alternative to the semantic versioning model, because breaking changes can’t be defined. Revisions need to meet an API Providers “Change Level Agreement”
- #8: So, how can API Mgmt help us deal with versions and revisions Developer portal is a customizable web site that provides tools and documentation to learn about API Used to advertise new versions API Contract is the interface. It’s the WHAT is changing. Changes in contract may be versions or revisions, depends on CLA Gateway acts as a façade to the API implementation isolate the backend Where revisions hide Let’s look into these three aspects a little bit more and then we will see how the product enables it
- #9: Developer portal is about facilitating on-boarding API community has recognized this as critical to adoption Change is irrelevant if no-one is using your API Self-service sign-on support for many IdPs Monitor for reliability and performance Review reports for usage Knowing what to change is as important as how
- #10: API Description formats define an interface. WSDL came first for SOAP -> protocol independent API WADL is XML based from the Java world OpenAPI (fka Swagger) JSON based, very popular MSFT using it in many products. Handle both revisions and versions
- #11: There are many ways to implement HTTP APIs Even on Azure there are different services Some fit better for different scenarios An how a feature needs to change can be a determining factor