Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

[APIdays Melbourne 2019] Delivering the Modern API: Know What it Takes

19 views

Published on

Do you know what it takes to deliver a Modern API to your customers? The rapid adoption of microservices has resulted in a significant uptake on APIs. Delivering an API in modern, heavily distributed systems require us to rethink the entire process of designing, testing, deploying and managing APIs.

This deck explores how the rapid adoption of microservices have impacted the architectures and processes involved in delivering APIs for the modern world. It will further discuss how the modern API,
- Gives back more value in return on investment.
- Is safer against more attack vectors.
- Is more robust and resilient against ever-changing requirements and other factors.
- Becomes more visible and observable through marketplaces and KPIs.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

[APIdays Melbourne 2019] Delivering the Modern API: Know What it Takes

  1. 1. Delivering the Modern API: Know What it Takes Nuwan Dias @nuwandias
  2. 2. • Delivering value to our customers is our #1 priority. • This requires lots of experimentation, trial and error. • We need to build a platform that allows us to fail fast. • A decentralized micro platform would give us the agility we need to do this. Modern Businesses are Consumer Driven Image source: newsd.in
  3. 3. The Journey Towards a Trillion Endpoints CONSUMER DEMAND SUPPLIERS DISAGGREGATE ARCHITECTURE TO MEET DEMAND Scale and agility are pushing app disaggregation... …that makes hybrid integration the unspoken challenge of all cloud services MONOLITHIC BUSINESS APP ENTERPRISE APPS DEPARTME NTAL APPS SAAS APPS PUBLIC / PRIVATE APIS SERVERLESS & MICROSERVICES 1970s | MAINFRAME 1980s | IT AWAKENING 1990s | INTERNET 2000s | MOBILE 2010s | IoT/AI 2020+ | DIGITAL NATIVE 1 10 102 103 105 109
  4. 4. Managing the Delivery of a Trillion Endpoints • A cell is a collection of components • It is independently deployable, manageable, scalable and observable. • Intra-cell communication is allowed without boundaries. • Inter-cell communication is only allowed via the Cell gateway. • Components within a cell are reusable and can instantiate in multiple cells. • Capabilities of a cell must be exposed as network accessible endpoints. • A cell is developed and managed by a single team. Cellular architecture: https://thenewstack.io/cell-based-architecture-a-new-decentralized-approach-for-cloud-native-patterns/ Cell
  5. 5. Types of Components in a Cell ● Cell gateway ● End user applications ● Microservices ● Serverless functions ● Legacy services ● Data repositories Cell
  6. 6. Traditional Delivery Model of an API What we follow today mostly is a top down approach to delivering APIs API design and documentation Application development API publishing API discovery and consumption
  7. 7. ● Developer/Code first APIs. ● CI/CD from day one. ● !SOA Agile Enterprises Require Bottom-up Delivery of APIs Build, Deploy, Test, Repeat API Documentation Publish API Build Applications
  8. 8. Governance
  9. 9. Governance Control Plane DataPlane API Lifecycle Manager API Portals Microservice API API API Microservice Microservice
  10. 10. Composability
  11. 11. Composability API Microservice REST/HTTP) Microservice (gRPC) Microservice (WebSockets) Data Services Message Queues
  12. 12. API Metrics to care about ● Latency ● Boot-up delay ● Independence/Isolation ● State replication API Scale API API APIAPIAPIAPIAPI
  13. 13. Availability
  14. 14. Insights Monitor Requests Control Access Scale Services Diagnose Errors Evaluate Business Objectives Realign APIs Insights Precautions Actions
  15. 15. Summary • Delivering value to our customers is our #1 priority. • Transitioning into decentralized, micro architectures give us the ability to experiment more. • Modern APIs are developed bottom-up, giving more prominence to the API developer. • The control plane allows us to govern APIs. • APIs should be composable, collecting heterogeneous services. • API security is 3 fold. Content inspection, identity verification and pattern analysis. • APIs should be easily and quickly scalable for cost effectiveness in the cloud native world • 9’s availability is no more. Demand is for 100% availability. • API insights help evaluate business objectives against alignment of APIs.
  16. 16. "Action and adaptability create opportunity" - Garrison Wynn
  17. 17. THANK YOU wso2.com

×