Service Mesh (Why and When?)

Microservices vs Monolith

Taken from experfy

Challenges of Microservices

The fallacies are: 
1. The network is reliable.
2. Latency is zero.
3. Bandwidth is infinite.
4. The network is secure.
5. Topology doesn't change.
6. There is one administrator.
7. Transport cost is zero.
8. The network is homogeneous.
  1. The responsibility of security is left on developers to establish protocols for communication between services.
  2. Error handling for the network is not coded in applications.
  3. Lack of a single authority.
  4. Bottlenecks created by a lack of rate-limiting and caching.

Service Mesh

Service Mesh Features

When do you need service-mesh

Summary

--

--

--

Bikes, Tea, Sunset, IndieMusic in that order. Software Engineer who fell in love with cloud-native infrastructure.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Milestone 1 -Day 1

Importing an SPM package into your iOS project

What is DataOps? — Definitions and Ambiguities.

Joining Multiple Agora Channels in Unity

Behind The Screens: Kate Sicchio

Uninstall Docker

TooNFT introduces decentralised webtoon platform to Web 3.0 via the Toomics Ecosystem

Unity Trajectory Prediction (Simulation Method)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
ADIL RAFIQ

ADIL RAFIQ

Bikes, Tea, Sunset, IndieMusic in that order. Software Engineer who fell in love with cloud-native infrastructure.

More from Medium

Where do Kubernetes Clusters hold significance in your app modernization journey?

From Monolith to Kubernetes Architecture — Part II — Dockerfile

Creating Spring Boot container in a minute with Cloud Native Buildpacks for Azure Container…

What Is GitOps?