Why Vertical Slice Architecture? Nobody wants to deal with a system that is hard to change and easy to introduce bugs because it's a spaghetti code mess of various technical concerns. Clean Architecture is popular because it separates concerns into many different layers. But why are we organizing code by layers? Does adding a new feature require you to modify files across multiple projects in your UI, business, and data access layers? Vertical Slice Architecture is about how you organize code and focus on features instead of technical layers will make your system easier to change.
🔗 EventStoreDB
[ Ссылка ]
🔔 Subscribe: [ Ссылка ]
💥 Join this channel to get access to a private Discord Server and any source code in my videos.
🔥 Join via Patreon
[ Ссылка ]
✔️ Join via YouTube
[ Ссылка ]
0:00 Intro
0:58 Layers
7:01 Coupling
15:35 Cohesion
30:27 Boundaries
37:53 Indirection
#softwarearchitecture #softwaredesign #cleanarchitecture
📝 Blog: [ Ссылка ]
👋 Twitter: [ Ссылка ]
✨ LinkedIn: [ Ссылка ]
📧 Weekly Updates: [ Ссылка ]
Vertical Slice Architecture, not Layers!
Теги
Vertical Slice Architecturesoftware architecturesoftware designcqrsevent sourcingdesign patternssoftware architectprogramming.netsoamicroserviceskafkaevent driven architecturemessaging patternsservice oriented architecturemicroservice architecturedomain-driven designenterprise service busvertical slice archetectureonion architecturelayered architectureclean architectureports and adapters
