Domain Driven Design for Microservices

Domain Driven Design for Microservices

The domain-driven design practices establish a business context and guide the specification and development of enterprise business objects and microservices that represent standard interfaces to business objects. An integration platform provides the security, governance and structure necessary to publish those interfaces. Master data practices ensure that the business’ core entities are effectively defined and curated. Finally, 360° views of those core business entities is facilitated by a data virtualization layer that masks the complexity of the underlying business systems. Data governance, security and compliance and business process transformation are cross-cutting elements in the above architecture.

Benefits of these patterns:

  1. Complexity and implementation details for specific line of business systems are better encapsulated, reducing the scope and impact of change to those systems.
  2. An ‘integration platform’ approach allows for improved standardization, greater transparency and visibility, and more direct application of security policies than a distributed approach.
  3. Domain-driven design practices help ensure that IT systems and interfaces are well aligned to the business processes and capabilities that they represent.
  4. Master data practices ensure that there are common definitions and clear stewardship of data that is used across a variety of line-of-business systems.
  5. A 360° view of business entities across systems is a strong business enabler, and helps to shield consumers from complexity in the underlying systems.

References

https://medium.com/design-and-tech-co/implementing-domain-driven-design-for-microservice-architecture-26eb0333d72e

https://medium.com/inato/an-introduction-to-domain-driven-design-386754392465

https://microservices.io/patterns/data/saga.html

要查看或添加评论,请登录

社区洞察

其他会员也浏览了