2021-07-25 16:16:00
Accidental complexity is stuff
you have to do, like builds and infrastructure configuration and so forth, whereas essential complexity is things like the code your customers want you to deliver. We as a developers want to do essential 100% of the time and throw everything else over the fence to other teams. Now with microservices it become a harder thing to do, but service mesh can solve some of the problems.
"Service mesh" is an umbrella term for products that seek to solve the problems that microservices’ architectures create. These challenges include security, network traffic control, and application telemetry.
Service mesh is typically implemented as a scalable set of network proxies deployed alongside application code (a pattern sometimes called a sidecar). These proxies handle the communication between the microservices and also act as a point at which the service mesh features can be introduced. They trying to decouple the platform-level features from the application itself.
For those who's interested this is a good article on the evolution and current problems that service mesh is solving.
But yeah, you got it — it's another layer of problems, probably more complex, but who cares? DevOps can handle that, right? Right?!
208 views13:16