Distribu-ready with the Modular Monolith - Layla Porter - NDC London 2024

This talk was recorded at NDC London in London, England. #ndclondon #ndcconferences #developer #softwaredeveloper

Attend the next NDC conference near you:

Subscribe to our YouTube channel and learn every day:

Follow our Social Media!

#architecture #microservices #web #dotnet

The past few years have seen huge hype around distributed systems and microservices.

Pre-emptive implementation of a distributed architecture has led to many engineering teams struggling with vast complexity and sadly for many, the dreaded "Distributed Monolith".

Some teams are in such a pickle that they are even reverting their distributed applications back to a monolith.

I'm all for designing and developing for future growth, but there is a better way than diving straight into distributed architecture.

Behold, the Modular Monolith.

By design, the modular monolith is "distribu-ready" and in this session, we'll cover the design principles and implementations that make the modular monolith one of the best options for future-proofing your application whilst minimising complexity.

[dcuccia]

Nice talk. Take-home point at minute 40 - you can start with a mediator to manage complexity within a monolith, and then migrate to a message bus when you have the need to be more distributed.

[vincentcifello]

Logical != Physical

Mediator pattern does not change the fact that the modules are actually calling each other. The coupling is just hidden.

Fat events for inter-module communication indicates incorrect boundaries. If the Kitchen needs the Order data, then why are they separate? Why doesn’t the Kitchen own the data it needs to perform its functionality?

The repeated error in these talks is the idea that the service boundaries can just be chosen (order, kitchen, etc) when they really need to be discovered based on business capabilities.

Hopefully, the wave of faux modularity will soon be coming to an end.

The only difference between a truly modular monolith and Microservices should be the physical deployment.

[pawerobak]

35:48 it is the first time I saw DbContext as Singleton ....

[allanwind]

First you waste time taking a photo, then you threatening the audience multiple times (in jest), and then the first slide that that I land on says your images are AI generated. Bounced @ 1m21s. Thumbs up if you beat my improve on my record. I humbly suggest NDC adapt a minimum quality standards for talks.