Hands-On Microservices with Kubernetes

Managing cross-service dependencies

Cross-service dependencies are often well defined and documented as internal APIs. However, subtle changes to the implementation and/or to the contract can significantly impact other services. For example, if we change the structs in object_model/types.go, a lot of code might have to be modified. In a well-tested mono-repo, this is less of a problem because the developer who makes the changes can ensure that all the relevant consumers and tests were updated. Many systems are built out of multiple repositories, and it might be challenging to identify all the consumers. In these cases, breaking changes can remain and be discovered after deployment. Delinkcious is a mono-repo, and it is actually not using ...