Overview of API Management Architectures
•Download as PPTX, PDF•
1 like•535 views
APIs are fueling innovation and digital transformation initiatives. With the explosive growth in APIs, developers and architects are employing different kinds of architectures to process API calls. Attend this session to learn about commonly deployed API Management architectures to process API traffic. Type 1: Centralized data plane and control plane. Type 2: “Hybrid” architectural approach that involves some processing at the edge by microgateways to process API calls between microservices. Type 3: Decoupled data plane and control plane resulting in no need for microgateways or databases to process API calls.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Overview of API Management Architectures
Similar to Overview of API Management Architectures (20)
More from Nordic APIs
More from Nordic APIs (20)
Recently uploaded
Recently uploaded (20)
Overview of API Management Architectures
- 1. Overview of API Management architectures Karthik Krishnaswamy, Director, Product Marketing, NGINX
- 2. APIs Are Experiencing Explosive Growth Source: ProgrammableWeb
- 3. Rise of API traffic 3 State of the Internet/Security 2019 report from Akamai 83% if Internet traffic is API traffic
- 4. API as a source of revenue 4 Source: 2014 Search Security article: https://searchsecurity.techtarget.com/news/2240222882/API-gateways-emerge-to-address-growing-security-demands 50% of Salesforce’s revenues come from APIs 90% of Expedia's revenues come from APIs
- 5. API Management API Management Definition & Publication Security Traffic Management (API Gateway) Ongoing Monitoring & Maintenance Analytics to Assess Value of APIs Onboarding (Dev Portal) 5
- 6. API Management Control Plane 6 Centralized Data Plane and Control Plane Data Plane - API Gateway to mediate API traffic API Control & Governance API Client API Endpoint • Content-based routing • Service Level Agreement (SLA) monitoring and enforcement • Fine grained access control • Quota management, traffic throttling, and load balancing API Monitoring API Transformation UI
- 8. Microgateways for microservices 8 B C A DevOps Team- owned • Load balancing • Service Discovery • Authentication per API • TLS Termination • Routing • Rate limiting API Management
- 9. API Management Control Plane 9 Decoupled Data Plane and Control Plane Data Plane - API Gateway to mediate API traffic API Control & Governance API Client API Endpoint • Content-based routing • Service Level Agreement (SLA) monitoring and enforcement • Fine grained access control • Quota management, traffic throttling, and load balancing API Monitoring API Transformation UI API Client API Endpoint
- 10. API Gateway handles all these functions.. 10 TLS termination Client authentication Fine-grained access control Request routing Rate limiting Load balancing Service discovery of backends Request/response manipulation
- 11. Advantages of the Decoupled Data Plane and Control Plane Approach 11 • High Performance • Same high performance regardless of where API GW is deployed (whether to handle N/S traffic or E/W traffic) • No need for additional software components such as microgateways • Small API GW footprint • Reduces complexity
- 12. Deployment Pattern Options Centralized Data Plane and Control Plane + Monoliths with centralized governance - Not suitable for microservices, Large footprint Hybrid approach with Microgateways + DevOps teams, high-frequency updates, Lightweight - Yet another component to manage, Hard to achieve consistency, authorization minefield Decoupled Data Plane and Control Plane + Ideal for N/S and E/W traffic, No additional components, Performant, Lightweight - Can’t integrate with traditional API Management systems
- 13. Google Cloud Endpoints Axway IBM DataPower Kong Red Hat 3scale Torry Harris NGINX Powers many API Management Solutions 13
- 15. 15 Thank You Karthik Krishnaswamy: k.krishnaswamy@f5.com LinkedIn: https://www.linkedin.com/in/kkrishnaswamy/
Editor's Notes
- Programmable web has been tracking HTTP APIs since 2005 – it’s the largest API directory on the web As you can see, the growth of public-facing APIs shows no sign of slowing down With about 200 new APIs per month for the last 4-5 years
- 2018 Global CIO Report, 800 CIOs, large enterprises Vanson Bourne & Dynatrace overcoming the hyper-complexity of modern cloud-centric ecosystems
- Microservices is an approach to software architecture that builds a large, complex application from multiple small components that each perform a single function, such as authentication, notification, or payment processing. Each microservice is a distinct unit within the software development project, with its own codebase, infrastructure, and database. The microservices work together, communicating through web APIs or messaging queues to respond to incoming events. You break down a monolith into a number of miroservices – each performing a single function. What are the benefits of this approach: Resilience: Better fault isolation; if one microservice fails, the others will continue to work. whole system is not impacted or goes down when there are errors in an individual part of the system. The Circuit Breaker pattern wraps a protected function call in a circuit breaker object, which monitors for failures. Once a failure crosses the threshold, the circuit breaker trips, and all further calls to the circuit breaker return with an error, without the protected call being made at all for a certain configured timeout. Reusability and Scalability: Better scaling - different parts of the system can be scaled independently Improved agility: Software built as microservices can be broken down into multiple component services, so that each of these services can be deployed and then redeployed independently without compromising the integrity of an application. That means that microservice architecture gives developers the freedom to independently develop and deploy services. Different teams can be working on different components simultaneously without having to wait for one team to finish a chunk of work before starting theirs . This shortens cycle times.
- Works well with cloud deployments because you can utilize the simple, native load balancer E consumes F in the same way as an external client Particularly good for widely distributed deployments where service E and service F are deployed far away from one another Be careful with authN per API – because you’ll end up with at least as many authN methods as you have APIs
- So first, just as a level-setting exercise Let's cover the 8 essential functions of an API gateway
- So what have we learnt? Each approach has merits…
- These vendors all use NGINX as the network-level proxy in their API gateway Different approaches We will use our expertise of NGINX, and NGINX Plus features to do this in a NGINX-native way wherever possible. Lua/njs where it makes sense.
- NGINX Plus is the core data plane that’s a load balancer, API gateway, WAF, reverse proxy and content cache. NGINX Plus delivers high performance for your applications in a manner that’s highly resource efficient – very low resource utilization. Controller provides configuration, monitoring and troubleshooting capabilities if you deploy NGINX Plus as load balancers. Controller offers full API lifecycle management – to define, publish, manage API traffic, monitor and analyze API usage. A service mesh provides governance, security, and control for environments with lots of microservices. A upcoming NGINX Controller module will manage and monitor NGINX Plus service meshes, apply microservices traffic policies, and simplify workflows.
- NGINX Plus is the core data plane that’s a load balancer, API gateway, WAF, reverse proxy and content cache. NGINX Plus delivers high performance for your applications in a manner that’s highly resource efficient – very low resource utilization. Controller provides configuration, monitoring and troubleshooting capabilities if you deploy NGINX Plus as load balancers. Controller offers full API lifecycle management – to define, publish, manage API traffic, monitor and analyze API usage. A service mesh provides governance, security, and control for environments with lots of microservices. A upcoming NGINX Controller module will manage and monitor NGINX Plus service meshes, apply microservices traffic policies, and simplify workflows.