Getting Started with Modular Monoliths in .NET 

Wow, thank you! This course should be a very nice extension, but much more advanced.

Apprecaite it, and returning the love back! 😁

Hope so! Starting work on it today 🤞😁

Glad you liked it!

Had to set the record straight 😁

Glad it was helpful!

About a ~month out from now, lots of work ahead

​@@MilanJovanovicTech Please hurry up with the course😊😊

Thank you 🤗

Thank you very much! :)

Glad you enjoyed it :)

Glad you liked it

I talked about the general idea here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-tKEF6xaeoig.html You can see the IServiceInstaller concept. The IModuleInstaller is the same thing, just implemented for each module.

@@MilanJovanovicTech Thank you for quick reply

Thanks a lot, glad you think so 😁

Dumbest take ever 😂

@@MilanJovanovicTech You're entitled to your opinion, but I'm sticking to mine - modular monoliths are nonsense. Either break it up or stick with it, don't bother half-assing it, it's only going to make everyone's life a misery if you do.

I do feel the same... just by enforcing that monolith code now will not be horizontal does not increase the efficacy magically. If you already have the infrastructure to manage and operate a Microservice - that's clearly the best. If you can manage the Microservice at par, then Nano service would be the way.

Look at the Figma Database issues, you'll know what I'm speaking. Vertical scaling is not an effective scaling. It has an upper ceiling.

@@AravindhKumar007 Careful, don't go having a different opinion to the OP - he's going to tell you it's a dumb take. This guy is a hack and there's no point engaging with him.

Thanks a lot! :)

Yes, I agree there's a tradeoff to be made here

The 7 lessons are from the bonus course. It's a condensed version of the main one, from a slightly different angle.

Coupled stuff goes together, check my longer videos on Modular Monoliths.

Will do, at some point :)

You never had the ability for granular scalability with any monolith application. It's all or nothing.

Thank you! 😃

They may have the same name, but if the namespaces is different it's not the same type. It's actually something I will touch on in a future video, where I will implement the Outbox pattern like that.

​@@MilanJovanovicTech That's true, but I'm sharing using an Outbox from a common package so I don't have to implement it per package, I can't register an Outbox per module since the namespace will be the same right? Is what I'm doing already the only way(creating wrappers per module)? It's very annoying do it like that lol. And there's another thing I'm confused about if you could spare some time, do you build all objects and their Dependencies in the Composition Root? I was considering another alternative since the Composition Root was getting too messy. Is using Inversion of Control and then constructing the object using a Factory which provides all the non dynamic parameters, and dynamic parameters as parameters in the build fuction, a nice approach? In the Composition Root I would then mostly pick the implementations I need for the abstractions. This way the smaller stuff like, for example, Mappers(for mapping between Domain and Database Mpdel) of a Repository dont' have to be added in the Composition Root, making it less cluttered imo. Any advice that you can give on these. Sorry for making you read this big block of text if you did read it and thanks :)

@@yaminnather521 I usually implement an extension method that configures DI per module. And then register all the modules from the composition root. The reason for this is decoupling the modules, so I can easily pull out one module and move it into a separate application. Does that make sense? It's quite common to duplicate stuff between modules, if you want to make them decoupled and independent.

​@@yaminnather521if you are calling the exact same DI registration code from two places, most likely you could just replace AddXY calls with TryAddXy, and should work, since the latter won't register it second time. Of course this only applies if the dependency registration is the same.

@@MilanJovanovicTech Yeah that makes sense. Thanks.

Implement that functionality in a single module?

It's a limitation of Teachable (the platform I'm using), so not much I can do about it :/

I see@@MilanJovanovicTech . So not an option to change the platform? :) Have you tried watching videos that has a small player and then you have to maximize the whole browser, not allowing you to multi-task or even code-along with you? :) I hope you understand.

@@PinoyDevAko Not an option to switch platforms. There is an option to see how I can increase the default size. It's something I'm looking into.

Thank you @@MilanJovanovicTech . Again you're wonderful and one of the best out there.

That's a pretty good signal that your module boundaries are probably wrong. You shouldn't have to talk to other modules so much that it impacts your performance negatively. Let's do a thought experiment. If that was a microservices system, what would you do?

Yes

In this case, it's in-process behind a MassTransit abstraction. But because of this, I can just add a RabbitMQ instance, update MassTransit to connect to it, and all else works the same

I guess the same way you would do it with microservices. create users table in orders.* schema or access it through api of users module

I'll explain how in a future video. I recommend reading this in the meantime: www.milanjovanovic.tech/blog/modular-monolith-communication-patterns TL;DR 1) Query the Users module to get the data. This should be done through a public API 2) Duplicate the data in both modules somehow

ad1 What if I return a list of orders with different users? Should I ask about each one separately? ad2 Duplicate the data: and there is additional work to maintain current data between modules. I'm thinking that I want more information than just username when ordering. E.g. avatar, account creation date, etc. In the case of database queries, this is very simple. Does this separation introduce too much complexity?

@@grzegorzr3621 Which of the two would you choose in a microservices system?

​@@MilanJovanovicTech I don't know. I don't know about this.

Come to the, erm..., modular side? 😂 lol

I wouldn't consider that a modular monolith

It's shared on Patreon

Request-response is sync, however way you look at it. Async would imply processing messages outside of the normal request flow. You'd process a 'UserRegistered' event, and store that info in the other module as a local copy. Then, you can query from the local copy when you need user data.

@@MilanJovanovicTech this can be very very complex..thanks!

Excalidraw for the "shiny ones" and draw.io for the C4 diagrams (but you can do C4 diagrams in other tools)

"Tight coupling" slide is supposed to show a 'mess' where any component can call any other component. Which introduces a lot of other problems I'm sure you're well aware of. The "Method calls" slide simply argues that instead of allowing components to freely call each other, we define a specific contract for how they communicate. The coupling is still there, but it's clearly defined and only in one place. This makes it much easier to control, expand, and manage second-level effects. I'm also unsure if you're confused by what I refer to as a Module. A module is not one class/object. A module is a logical concept inside the monolith, grouping together many components that provide the module's functionalities.

Thanks!

Sorry 'bout that 😅 I was applying ROP on this project.

I share all the source code on Patreon, and for some videos you can find it in the description

You don't necessarily have to. And the built-in DI doesn't support that. You have to use something like Autofac.

Read this: www.milanjovanovic.tech/blog/modular-monolith-communication-patterns I'll release a few more videos soon.

Shared it on Patreon

@@MilanJovanovicTech thanks

Desperate cry? We've been building modular monoliths way longer than we've been building microservices

He had said some months ago that he would talk about this topic in the future. So I mean he had planned this video before that course you've pointed out.

Who cares though? Content creators of a similar type of content are obviously going to make videos on topics trending in their domain, right? They don't care if someone else covered a similar topic already, and why should they? It's not a big deal. The thing we should be worried about imo is whether they are making good content or not, and covering the topics well. But if the videos are the same and not just the idea of the video, then I wouldn't like it ig.

When throwing out serious accusations like that, I expect you to do your due diligence (which I'm sure you did, of course, why else would you accuse me of stealing without proof). So, here are a few references in case you missed them (I produce a lot of content, so I know it's easy to miss some). Here's an online talk about Modular Monoliths I held on Jan 31, 2023: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-YGbO9dTVE7Y.html Here's another in-person talk I held in Norway (you'll never guess the topic) on Apr 26, 2023: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-23QlLwDaOEk.html I have been writing about Modular Monoliths on my blog for months: - Modular Monolith Communication Patterns (August 5th, 2023): www.milanjovanovic.tech/blog/modular-monolith-communication-patterns - Monolith to Microservices: How a Modular Monolith Helps (September 23rd, 2023): www.milanjovanovic.tech/blog/monolith-to-microservices-how-a-modular-monolith-helps - Modular Monolith Data Isolation (December 9th, 2023): www.milanjovanovic.tech/blog/modular-monolith-data-isolation I've also been teasing a Modular Monolith course for months, so I have nothing to hide. Second, if you accuse someone of "stealing content" based on recency of releasing something: - My Clean Architecture course came out in August 2023 - Dometrain released two courses later that year So, who's copying who? I'm sure you'll agree this is a silly argument. I'm certainly not saying they're copying me, so why should the reverse hold true. I have a lot of practical experience using CA or MM, and I want to share my perspective. I'm confident the course will be very different from dometrain one. Third, and most important, it's a free market. If I want to release a Modular Monolith course, I can. Let the market decide which one is more valuable. Stay awesome. :)

That’s a pretty serious accusation. Modular monoliths is a popular architecture right now. There’s going to be more than one content creator covering it.

@@MilanJovanovicTech that's what I tried to say, I'm not blaming. I'm more like asking, maybe my words are not too clear, otherwise I would be directly reporting. I also pointed the fact that that there's no evidence