You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Places, where the current implementation can do better, are inter-service communication, service authorization, security, load balancing, and improved monitoring. By integrating the Service mesh layer above the existing Kubernetes architecture, this can be easily achieved.
Proposed solution
Desired improvements:
Load Balancing - With just Kubernetes, the load balancing is done in a round-robin fashion. The other way to do is choosing pods at random. There are much better ways to balance the loads and by integrating our current architecture with Service mesh, we can distribute the load using multiple options such as Random, Weighted, Fewer requests, etc.
Service Authorization & Authentication - Using service mesh, inter-service communication restrictions can be imposed.
Monitoring - Using a service mesh, one can collect and provide various system/network metrics.
Sidecar Proxy - The inter-service communication is done through a side-car. Since their job is to communicate with other microservices, the burden on the microservice can be reduced.
Encryption - Using service mesh, secure inter-service communication can be implemented. This is done using encryption through a service mesh.