Enterprise API Management

Independent runtime

In microservices architectures, services should be fully decoupled, not just in terms of specific business functionality (bounded context) but also with regard to where they run. For example, if all services share a single monolithic runtime (for example, an ESB), then in order to scale a single service, the entire monolith has to be scaled. Likewise, if the common runtime (the ESB) goes down, then all services are equally affected.

This problem becomes even more obvious when services from different bounded contexts share the common runtime. In order to separate concerns and avoid putting all eggs in one basket, each service must therefore run in its own runtime, thus allowing services to be independently:

• Scaled or shrunk ...