-
Refactor to modules
Let’s look quickly at typical application: Although at first sight it looks many classes and packages this is very simplified, as you know from real projects. What we can see? Controllers, services, repositories, entities, dto’s, other classes. Every application has that building blocks. Can we see what are the relations, dependencies? No. Can we see…
-
From subdomains to bounded contexts
Domains/subdomains belong to the problem space. Bounded contexts are part of solution space, for the problems in subdomains. In an ideal situation, when we have all requirements or the most important requirements and processes, and we correctly discover the subdomains, most often the problem space covers the solution space, its 1:1 relation: I think this…
-
What is the bounded context?
In simple words, it is part of the system in which we solve business problems. Technically speaking, it could be a microservice code repository, in which we write code that implements business requirements. ‘Bounded context’ is a context with emphasis on the boundary of the context, therefore it is called a bounded. If you do…
-
Protected: Modules everywhere – the best pattern ever
There is no excerpt because this is a protected post.
-
Protected: Modules in java
There is no excerpt because this is a protected post.
-
Protected: What is a module?
There is no excerpt because this is a protected post.
-
Protected: Why we need modules (aspect three)
There is no excerpt because this is a protected post.
-
Protected: Why we need modularization (aspect two)
There is no excerpt because this is a protected post.
-
Protected: Why we need modularization (aspect one)
There is no excerpt because this is a protected post.
-
Protected: Modularization benefits
There is no excerpt because this is a protected post.