Don't be fooled! That's NOT an Aggregate in Domain Driven Design

Do you get frustrated that you have to open multiple files across multiple layers to make what seems to you like a simple change? One of the culprits for this is following structure and templates that apply patterns or concepts to solve problems you might not have. One typical case of this is using aggregate from domain drive design. In this video, I'll give some examples of where an aggregate can make sense and where it's not and adds useless indirection.

🔗 EventStoreDB
https://eventsto.re/codeopinion

🔔 Subscribe:    / @codeopinion  

💥 Join this channel to get access to source code & demos!
   / @codeopinion  

🔥 Don't have the JOIN button? Support me on Patreon!
  / codeopinion  

📝 Blog: https://codeopinion.com
👋 Twitter:   / codeopinion  
✨ LinkedIn:   / dcomartin  
📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo...

0:00 Intro
0:51 Indirection
3:20 Fake Aggregate
6:42 Consistency Boundary

#softwarearchitecture #softwaredesign #domaindrivendesign

'image: Flaticon.com'. This cover has been designed using resources from Flaticon.com