Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureEasy
A company is migrating its monolithic application to a microservices architecture. They need a way to manage cross-cutting concerns like traffic management, security, and observability for inter-service communication without modifying the application code itself. Which cloud native component is best suited for this purpose?
- AService Mesh
- BMessage Broker
- CAPI Gateway
- DContainer Registry
Show answer & explanationAnswer & explanation
Correct answer: A. Service Mesh
A service mesh provides a dedicated infrastructure layer for handling service-to-service communication, offloading concerns like traffic management, security, and observability from individual microservices.
Why the other options are wrong
- B. A message broker facilitates asynchronous communication but doesn't provide the comprehensive traffic, security, and observability features of a service mesh.
- C. An API Gateway manages incoming external requests, not inter-service communication within the cluster.
- D. A container registry stores container images, which is unrelated to runtime communication management.
Service Mesh
A dedicated infrastructure layer that handles service-to-service communication within a microservices architecture.
- Manages traffic, security, and observability.
- Decouples network concerns from application code.
- Often implemented with sidecar proxies.
- Examples include Istio, Linkerd, Consul Connect.
Memory trick: The service mesh weaves a network for your services to talk securely.