| ▲ | lukevp 6 hours ago | |||||||
Shared telemetry library, you realize that you are missing an important metric to operationalize your services. You now need to deploy all 140 to get the benefit. Your runtime version is out of date / end of life. You now need to update and deploy all 140 (or at least all the ones that use the same tech stack). No matter how you slice it, there are always dependencies across all services because there are standards in the environment in which they operate, and there are always going to be situations where you have to redeploy everything or large swaths of things. Microservices aren’t a panacea. They just let you delay the inevitable but there is gonna be a point where you’re forced to comply with a standard somewhere that changes in a way that services must be updated. A lot of teams use shared libraries for this functionality. | ||||||||
| ▲ | jrnng 6 hours ago | parent [-] | |||||||
These are great examples. I'll add one more. Object names and metadata definitions. Figuring out what the official name for something is across systems, where to define the source of truth, and who maintains it. | ||||||||
| ||||||||