Yeah, I completely agree. I mean, there are whole books on the topic! (one I enjoyed a lot was oreilly.com/library/view/implement..., which goes quite in-depth into bounded contexts).
In the project that inspired this article we decided to create the most granular domains we could (f.i. Question, Answer and Comment were each a totally isolated "microservice"). This has been quite effective, but I couldn't claim that it's the right fit for all codebases.
In our case, we have a combination of synchronous RPC calls (where one domain can call another) and asynchronous event listeners (one domain can react to what happens around it).
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.
Yeah, I completely agree. I mean, there are whole books on the topic! (one I enjoyed a lot was oreilly.com/library/view/implement..., which goes quite in-depth into bounded contexts).
In the project that inspired this article we decided to create the most granular domains we could (f.i. Question, Answer and Comment were each a totally isolated "microservice"). This has been quite effective, but I couldn't claim that it's the right fit for all codebases.
That book looks interesting. How are you handling inter-domain communication?
In our case, we have a combination of synchronous RPC calls (where one domain can call another) and asynchronous event listeners (one domain can react to what happens around it).