Its not mandatory but its essential
Intro
A service mesh is an infrastructure layer that manages how services talk to each other inside Kubernetes.
It matters because as applications grow into many microservices, communication becomes harder to secure, monitor, and control.
The Core Problem in Kubernetes
Kubernetes handles deployment, scaling, and networking.
But it doesn’t handle advanced service-to-service concerns by default.
Inside the cluster:
- Monitoring and retries must be added manually
- Pod-to-pod traffic is often plain text with no security
As the number of microservices grows, this becomes difficult to manage.
Application Layer vs Platform Layer
Application layer logic is what your service is built to do.
For example:
- Fetch user data
- Process payments
- Render a web page
Platform layer logic supports the app but is not the app itself.
Examples include:
- Encryption
- Traffic routing
- Authentication
- Metrics and logs
Mixing these two layers increases complexity.
Why You Need a Service Mesh
A service mesh is optional, but very useful in real-world systems.
Here are some of the main reasons teams adopt it.

