> I personally find that the service mesh value-prop is hard to justify for a serverless stack (mostly Cloud Run, but AWS Lambda too probably), and in situations where your services are mostly all in the same language and you can bake the features into libraries that are much easier to import.
If you’re running server less you already have 90% of what you’d get from a service mesh.
I will tell you that having seen what happens in big companies, baking distributed concerns into libraries always ends in disaster long after you’re gone.
When you have a piece of code deployed in 200 separate apps, every change requires tons of project management.
If you’re running server less you already have 90% of what you’d get from a service mesh.
I will tell you that having seen what happens in big companies, baking distributed concerns into libraries always ends in disaster long after you’re gone.
When you have a piece of code deployed in 200 separate apps, every change requires tons of project management.