Enterprise API Management

Service mesh

Having services that run independently of each other is undoubtably an important and fundamental capability within a Microservices Architecture. However, having an all-encompassing and single executable unit in support of a service bounded by a context can also be limiting and in many cases undesirable, as it couples different aspects of a service that may have to undergo change and deployments at a different pace, or might even have different scalability requirements, as is the case between reads and writes, where reads often have a much more dependent scalability need.

For this and many other scenarios, a service within a single-bounded context might have to be broken down into smaller (executable) pieces that bind directly ...