Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureMedium
A team is developing a new cloud-native application and wants to ensure that internal and external services can communicate securely and reliably, regardless of their underlying network topology or programming language. They also need capabilities like traffic management, policy enforcement, and observability without modifying application code. Which cloud-native component is best suited for this requirement?
- AContent Delivery Network (CDN)
- BService Mesh
- CMessage Queue
- DLoad Balancer
Show answer & explanationAnswer & explanation
Correct answer: B. Service Mesh
A service mesh provides a dedicated infrastructure layer for managing service-to-service communication within a microservices architecture. It enables capabilities like traffic management, policy enforcement, security (mTLS), and observability without requiring changes to the application code itself.
Why the other options are wrong
- A. A Content Delivery Network (CDN) caches and delivers static content to users based on geographic location, which is unrelated to internal service-to-service communication management.
- C. A Message Queue facilitates asynchronous communication between distributed components but doesn't handle traffic management or policy enforcement for direct service calls.
- D. A Load Balancer distributes incoming network traffic across multiple servers but doesn't provide fine-grained service-to-service communication control or observability.
Service Mesh
A configurable infrastructure layer for handling service-to-service communication, making interactions between microservices flexible, reliable, and fast.
- Adds capabilities like traffic management, security, and observability.
- Operates at the network level, typically using sidecar proxies.
- Decouples service communication logic from application code.
- Often used in Kubernetes environments.
Memory trick: The Mesh makes microservices marvelously managed.