The thing is that most of the time, we put too much things inside (like the data loading or the anti-corruption or the reporting…) Here is a list of the most recurring patterns I have discovered over time.Īnd finally, the holy grail, the one you look for because it creates value for your business, the key technical asset for your company: the business core context.Īll the projects I have worked with have a business core context. It’s the same principle, just at a different scale. Indeed, like in the hexagonal architecture, we have core stuff and surrounding stuff with adapters and/or anti-corruption layer. I believe these patterns can also be seen with a hexagonal approach.
#BOUNDED CONTEXTS HOW TO#
I usually use a strategic Domain Driven Design (DDD) approach to understand and classify this structure, resulting in some domains, subdomains and bounded contexts.īecause of this repetition, I think bounded contexts can be classified in patterns, and that these patterns can help to know the importance of the bounded context and how to build it in the most efficient way for the business. As a consultant I have the chance to do it in different gigs since a few years now, and I start to see repetitive patterns in the way companies are structured. After a decade of coding, I tend to believe that being able to discover and implement correctly bounded context is one of the main values I can bring to a company in my daily job.
0 kommentar(er)
