Time to learn about service meshes and microservices with Arijit Mukherji! 
What’s keeping us from a world of easy software development? Service mess! What can help? Service mesh!
The talk is going to be more conceptual in nature - we aren’t taking a deep dive into a single mesh framework. #reInvent
High level visual of how services utilizing a service mesh interact from @arijit_mukherji with good summary description with plenty of light humor thrown in. #reInvent
Common use cases for service mesh: error handling, load balancing, request routing, and security. By abstracting these capabilities to your mesh, teams no longer have to reinvent the wheel every time they build a new service. This is especially potent in polyglot #reInvent
Desired and discovered states rarely match. Embedding your telemetry system within the mesh helps us standardize and create standardized and repeatable feedback loops - @arijit_mukherji
Canary and blue green deployments are still done with manual steps. “What if we could express our intent through a defined automated workflow based on telemetry? This is being built into meshes today!” #reInvent
Lots of benefits for the runtime with mesh #reInvent
“One of the reasons we see slower adoption of Chaos Testing is the friction associated with setting up tests and minimizing blast radius. Mesh can simulate errors and other FIT situations” @arijit_mukherji Opinion: The friction is certainly present. Chaos isn’t cheap.
Now going over the three pillars of monitoring: metrics, logs/events, and trace. All of these suffer from the need for instrumentation per service. Mesh helps to mitigate and standardize.
Getting into some risks associated with mesh adoption. A lot having to do with the blast radius of a service mesh deployment. #reInvent
Originally a haiku about DNS but it could certainly apply with meshes with large deployments:
It’s not Service Mesh
There is a no way it’s Service Mesh
It was Service Mesh #reInvent
It’s not Service Mesh
There is a no way it’s Service Mesh
It was Service Mesh #reInvent
That said, service meshes are certainly picking up steam and investing in their use cases is valuable. They may enable a leapfrog for many orgs but stability and maturity in the space does need to improve. #reInvent
@threadreaderapp kindly unroll
