This is a very straightforward approach to architecting applications where there is exactly one point of entry into the application. There is a high chance that you are already using this in your ongoing projects. Monolith Architecture is probably used for 80% of the applications in existence. This was the reason that I got started writing articles about this architecture. Each of the modules follows a clean architecture design / Onion / Hex.Įssentially we would end up with a Solution that contains MultipleModules where-in each of the modules implements a variation of Clean / Onion Architecture. And yes, domain events are also included in the project using mediator Handler. CrossCutting concerns would use interfaces/events. One module cannot directly talk to the other module nor modify its table. As for the DB providers, Postgres / MSSQL will be used. Each of these modules has its own controllers/interfaces / dbContext. This needed breaking down the application to logical modules like Identity, Catalog, Sales, Inventory. The WebAPI application had to be highly modular to improve the development experience. But given the complexities of the mentioned architecture, we decided to stay away from it at least for the starting. Adapting to a Microservice architecture was the first choice we had. Modular development was a prime requirement for us when we got started. Having quite a lot of experience with POS & Inventory Management systems, we set out to build a full-fledged open-source system using our favorite tech stack and tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |