Solution & Project Structure of a Loosely Coupled Monolith

Here’s how a loosely coupled monolith can be structured in a .NET Solution with C# Projects. Each boundary is in a solutions folder with 3 projects. Implementation, Contracts, and Tests. All of which are class libraries. The two top level executable projects, AspNetCore and Worker are console applications that reference the implementation projects.

https://codeopinion.com/loosely-coupled-monolith/

🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

💥 Join this channel to get access to source code, demos, and slides!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

📝 Blog: https://codeopinion.com

📚 Book Recommendations

Domain-Driven Design
https://amzn.to/2QwG8sb

Patterns of Enterprise Application Architecture
https://amzn.to/3d8kMJj

Refactoring: Improving the Design of Existing Code
https://amzn.to/2NVdP5Q

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
https://amzn.to/3srUuZ6

RESTful Web Clients: Enabling Reuse Through Hypermedia
https://amzn.to/3d8Q96B

CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion

0:00 Intro
0:59 Boundary Projects & References
2:41 ASP.NET Core (Top Level)
3:08 Configure Services
4:25 Endpoints
5:45 Worker (Message Processor)
7:41 Overall Structure

#monolith #dotnet #csharp