Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic “ball of mud” systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds.
How to handle the dependencies between these disparate systems with different iteration cycles? Consider the “canoncial problem” in this scenario: microservice A (releases daily) depends on a couple of additions to backend B (releases quarterly).