

When a dependency is managed by a context to another one, a translator pattern is required for interpretation of the published language used by the context in dependency. How to maintain a flexible integration between bounded contexts?Įach context include a dedicated sub-service dedicated to each sub-domain. The dependencies between the domains is managed through functional interfaces to maintain a good level of isolation that allow exposure to change without big impact regarding the systems coupling. Infrastructure Layer: regarding the layers Data Services & Messaging, Data Abstraction and transversal SOA areas (Security & Access Control, Integration Middleware).Domain Layer: concerning the business data and rules of management of status.Include business logic about the processes performed by the IT system. Application Layer: include Application, Process & Orchestration and Services layers.Layer implemented by GUI delivered to user through interactive applications. User Interface Layer: regarding the direct point of contact with the user/beneficiary of a business process.Each domain context can include one or many components distributed in User Interface Layer, Application Layer, Domain Layer and/or Infrastructure Layer. The Information System includes several layers. The components of infrastructure layer can be shared (in terms of use) between several applications.

It can use an Infrastructure Layer through proxy design pattern. Each main can be supported by one dedicated application and sub-domain can be specifically managed by one or many applications.Īn application which supports a domain or a sub-domain can include an User Interface Layer, an Application Layer and a Domain Layer. The Freeduse architecture model is based on a Domain-Driven-Design approach. To know more, I invite you to read « Implementing Domain-Driven Design » book from Vaughn Vernon.

