If you're developing a Monolith or using a Monolithic Architecture doesn't mean it needs to be a big ball of mud. Most people equate a Monolith with a Big Ball of Mud because it's highly coupled and difficult to change. However, you can combat it by defining strict boundaries and logically decoupling those boundaries and the data that each boundary owns. To go even further you can loosely couple by leveraging asynchronous messaging between boundaries. Does this sound familiar? Like Microservices where each service has its capabilities database?

🔗 EventStoreDB
[ Ссылка ]

🔔 Subscribe: [ Ссылка ]

💥 Join this channel to get access to source code & demos!
[ Ссылка ]

🔥 Don't have the JOIN button? Support me on Patreon!
[ Ссылка ]

📝 Blog: [ Ссылка ]
👋 Twitter: [ Ссылка ]
✨ LinkedIn: [ Ссылка ]

0:00 Intro
0:32 Big Ball of Mud
1:18 Distributed Big Ball of Mud
2:02 Boundaries
4:03 Logical Decoupling


#softwarearchitecture #eventdrivenarchitecture #softwaredesign

свернуть