![]() ![]() If domains are where you have expertise and skills, then think of the context in which you apply them to solve a business problem. There are domains within these child domains with areas of expertise Bounded Context ![]() Supporting domains are key to us providing value in the core domain and generic domains are areas where there is expertise in the market which we can leverage You business and domains. Core domains are where we want to excel as a business and our specific skills here really differentiate us from the rest of the market. This can be a “core” domain, a “generic” domain or a “supporting” domain. The domain in DDD stands for the business domain we are modelling our software for. We look at what is DDD and how to apply it when designing new or simplifying existing software services (APIs, Microservices, Events) and integrations Domains In this post, we review some of the core DDD concepts and apply them to business software architecture. Using DDD is incredibly useful when designing services because it helps you rationalise the granularity of your software, the ownership boundaries and model interactions need to build de-coupled and reactive distributed systems If you are building or designing APIs, Microservices or integrating systems then Domain Driven Design (DDD) offers a valuable design technique for mapping business domains to build software services of value ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |