Answer the question
In order to leave comments, you need to log in
What resources to read or maybe books that describe the techniques for designing the application core?
I designed an application: I have modules that are not related to each other and I also have an application core that manages all these modules. That is, the modules do not have direct access to each other, they interact through the kernel.
That is, the core will be a kind of mediator, and the modules will be accessed through the facade.
Now I'm thinking about the inside of the kernel, but I would like to read the literature . Any advice?
The idea in the general case is this: there will be a queue in the kernel that will asynchronously call the necessary modules, the modules will process information, return the processed result. And so on, until the entire queue in the kernel is completed. It is expected that at the end of the queue the information will be in a ready (fully processed) form.
Answer the question
In order to leave comments, you need to log in
The first rule of designing an application core is to get rid of the application core and make normal components with a minimum of dependencies.
The second rule is to read what God Object is and slowly begin to understand the reason for getting rid of the core.
The third rule is to go read Clean Architecture/Clean Code, deal with the concepts of coupling/cohesion, etc.
ps sequential processing of data by multiple components can be solved through services - coordinators, through intermediaries (middlewares), a chain of responsibilities (Chain Of Responsibility), at least decorators in the end.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question