Desktop version

Home arrow Computer Science arrow Microservices Flexible Software Architecture

Collaboration between Bounded Contexts

How are the individual Bounded Contexts connected? There are different possibilities:

  • • In case of a Shared Kernel the domain models share some common elements; however, in other areas they differ.
  • Customer/Supplier means that a subsystem offers a domain model for the caller. The caller in this case is the client who determines the exact setup of the model.
  • • This is very different in the case of Conformist: The caller uses the same model as the subsystem, and the other model is thereby forced upon him. This approach is relatively easy, for there is no need for translation. One example is a standard software for a certain domain. The developers of this software likely know a lot about the domain since they have seen many different use cases. The caller can use this model to profit from the knowledge from the modeling.
  • • The Anticorruption Layer translates a domain model into another one so that both are completely decoupled. This enables the integration of legacy systems without having to take over the domain models. Often data modeling is not very meaningful in legacy systems.
  • Separate Ways means that the two systems are not integrated, but stay independent of each other.
  • • In the case of Open Host Service, the Bounded Context offers special services everybody can use. In this way everybody can assemble their own integration. This is especially useful when an integration with numerous other systems is necessary and when the implementation of these integrations is too laborious.
  • Published Language achieves similar things. It offers a certain domain modeling as a common language between the Bounded Contexts. Since it is widely used, this language can hardly be changed anymore afterwards.
 
Source
< Prev   CONTENTS   Source   Next >

Related topics