I've had a look at it. Pretty impressive in its scope. I had a similar idea to use Spring Events to communicate between the modules. Greetings from/to Munich.
How do you organize the "common sense" in this kind of infrastructure? I assume, there is some kind of eCommerce application locally that will supply some data, so you may need to know some detaily about the data organization. Modules need to know the currency you are using or simply understand each other. I assume you do not want those implementation details in the local code?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You may check out this project where I tried to build modular monolith based on principles of DDD.
github.com/ttulka/ddd-example-ecom...
I've had a look at it. Pretty impressive in its scope. I had a similar idea to use Spring Events to communicate between the modules. Greetings from/to Munich.
Thanks!
I have implemented communication via Spring Events in this fork:
github.com/ttulka/ddd-example-ecom...
It's a bunch of services that can be deployed either as a monolithic application or as microservices (docker compose or kubernetes).
How do you organize the "common sense" in this kind of infrastructure? I assume, there is some kind of eCommerce application locally that will supply some data, so you may need to know some detaily about the data organization. Modules need to know the currency you are using or simply understand each other. I assume you do not want those implementation details in the local code?