Map context DDD-

-Context Map- context map contains an integrated relationship between the project and they bounded context.

Two basic integrated relationship: upstream and downstream of the upstream downstream.

Organizational model and integration model definition:

  • Partnership (partnership): two bounded context of team either succeed together or fail together, these two teams is a partnership.
  • Sharing the kernel (shared kernel): sharing model and code.
  • Client side - the development of the supply side (customer-supplier development): upstream and downstream relationships.
  • Conformist (conformist): the relationship between the upstream and downstream, upstream of the downstream team no incentive to provide what the team needed.
  • Coating (anticorrupttion Layer) (ACL): Some relationships can not be successfully implemented, this layer serving as a proxy to your system upstream of the system.
  • Open Host service (open host service) (OHS): the definition of a protocol that allows you to access your other subsystems through the service agreement.
  • Published language (published language) (PL): complete integration announce a shared language exchange, commonly used with an open hosting services.
  • Find a new way (separate way): declare two contexts do not exist any relationship.
  • Big Ball of Mud (big ball of mud): model mixed together.

And mention that: subdomain and bounded context is best to keep one to one relationship.

Practice: identifying their bounded context that should not belong to the concept identified therein, these concepts in the context of the other, then the indicated relationship between the two limiting in the context of FIG.

Guess you like

Origin www.cnblogs.com/zzjimmy/p/10958604.html
map
Map
Map
map