My only reservation about this architecture as presented is the lack of cautions about the in-process calls from MediatR handler to MediatR handler. What seems to happen if goes unchecked is that teams make really granular choices about when to define a "module", usually matching their entities, so you end up with Module A's MediatR interface, who's getting data from Module B's MediatR interface, who's getting data from Module C's MediatR interface, etc. etc. When defining a new module, we need to stop for a second and think about whether it makes sense to define a boundary where we are about to. What would it look like in the future if this Mediatr call was replaced with an API call between boundaries? Would the architecture completely break down?
9:57 college taught you how to do it, for me there was nothing in this requirements level. I bet Visma does it, but they and everybody else just keep rejecting this past education bachelor/magister degree. At every job should try to apply that college taught experience, but it's really too much for me alone to keep that level of culture and there is not much choices in the facebook groups that keep the history from long ago. These careers are Uncommon quality, better than Common but not as good as Rare which are few or none at UŽT portal and there should be no barricades road blocks for anybody having a diploma/school finishing certificate gifted/Inspired by Branson
i dont understand how this helps with modularity. its looks like you have switched between BL calling BL to API mocking a call to API. how do you stop the devs from ruining your seperations ? what is forcing them to write code under this domain breakdown modularity? after all each domain holds refs to other domains no ?
![Kumamoto Masters Japan 2024 | Gregoria Mariska Tunjung (INA) [5] vs. Akane Yamaguchi (JPN) [2] | F](http://i.ytimg.com/vi/EIjZybhsWqA/mqdefault.jpg)
Very nice.. practical exploration of the "Modular Monolith" approach, highlighting the trade-offs and benefits.
I'm a big fan of Ardalis, from his courses on Pluralsight to his RUclips channel.
Excellent overview, thank you
Really great overview!
Excellent information.
Excellent, I'm looking forward to seeing the source code to be public. Thanks
Great crystal clear content. Thanks!
My only reservation about this architecture as presented is the lack of cautions about the in-process calls from MediatR handler to MediatR handler. What seems to happen if goes unchecked is that teams make really granular choices about when to define a "module", usually matching their entities, so you end up with Module A's MediatR interface, who's getting data from Module B's MediatR interface, who's getting data from Module C's MediatR interface, etc. etc. When defining a new module, we need to stop for a second and think about whether it makes sense to define a boundary where we are about to. What would it look like in the future if this Mediatr call was replaced with an API call between boundaries? Would the architecture completely break down?
Does the course or source code cover how you would go about unit testing this?
Mail-Outbox: Wouldn't it be better to replace the while loop and watch the mongodb change stream for inserts instead?
Great overview on the Modular Monolith!!! However I like SOLID a little more 😜!
9:57 college taught you how to do it, for me there was nothing in this requirements level. I bet Visma does it, but they and everybody else just keep rejecting this past education bachelor/magister degree. At every job should try to apply that college taught experience, but it's really too much for me alone to keep that level of culture and there is not much choices in the facebook groups that keep the history from long ago. These careers are Uncommon quality, better than Common but not as good as Rare which are few or none at UŽT portal and there should be no barricades road blocks for anybody having a diploma/school finishing certificate gifted/Inspired by Branson
i dont understand how this helps with modularity. its looks like you have switched between BL calling BL to API mocking a call to API. how do you stop the devs from ruining your seperations ? what is forcing them to write code under this domain breakdown modularity? after all each domain holds refs to other domains no ?