Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureHard
A global e-commerce company is migrating its legacy monolithic application to a cloud-native microservices architecture. They need a component that can act as a single entry point for all client requests, handle authentication and authorization, perform request routing to different backend services, and potentially implement rate limiting and caching. Which architectural component fulfills these diverse requirements most comprehensively?
- AService Mesh
- BAPI Gateway
- CLoad Balancer
- DMessage Broker
Show answer & explanationAnswer & explanation
Correct answer: B. API Gateway
An API Gateway is specifically designed to be the single entry point for clients, offering robust features like authentication, authorization, intelligent request routing, rate limiting, and caching, abstracting backend complexities from frontend applications.
Why the other options are wrong
- A. A Service Mesh manages inter-service communication within the cluster, not external client requests.
- C. A Load Balancer primarily distributes traffic; it doesn't typically handle authentication, authorization, or advanced routing logic.
- D. A Message Broker facilitates asynchronous communication between services, not direct client request handling.
API Gateway
A server that acts as a single entry point for a set of microservices. It handles requests by routing them to the appropriate service, and can also perform cross-cutting concerns like authentication, authorization, rate limiting, and caching.
- Single entry point for clients.
- Handles authentication and authorization.
- Routes requests to backend services.
- Can implement rate limiting, caching, logging, monitoring.
- Abstracts microservice complexity from clients.
Memory trick: Gateway guards the path to your services.