Domain Driven Design & NoSQL

on YouTube ↗20m

" summary

Argues that combining a document store and a graph database in a single multi‑model engine (ArangoDB) lets the storage match the domain instead of forcing tables and joins, with embedding for immutable value objects and edges‑as‑documents to record facts like “owned since 1978.” Claims this reduces the translation loss between domain experts and implementers, enables safe denormalization of aggregates, and shows a concrete, working alternative to heavy recursive SQL joins.

AI-written summary · about

" chapters (24)

1. 0:00Introduction
2. 1:08Language
3. 2:10DomainDriven Design
4. 3:02Building Blocks
5. 3:37About Lucas
6. 3:47The Lie
7. 4:34The Bridge
8. 5:18What is NoSQL
9. 5:45What is SQL
10. 6:23What is tuple
11. 6:53What is table
12. 7:38Domain world
13. 8:21Domain objects
14. 11:19Denormalization
15. 12:00tuples
16. 12:22embedding
17. 12:41document store
18. 12:53nested documents
19. 13:28Joins
20. 14:26Graphs
21. 14:50Graph Databases
22. 15:19Multimodal Databases
23. 16:43The Disconnect
24. 17:45The Procedure

" related talks

• 01h 00mFrom Relational Databases to NoSQLScott Davis · Great Indian Developer Summit 2015
• 18mGermany's Next Top Data ModelIan Plosker · Berlin Buzzwords 2012
• 01h 01mNoSQL: An AnalysisAndrew J. Brust · PASS Business Analytics Conference 2013
• 39mHandling Billions of Edges in a Graph DatabaseMax Neunhoeffler · MesosCon Asia 2016
• 18mFrom SQL to NOSQL - a gentle intro for DevsJoe Karlsson · Conf42 JavaScript 2020
• 45mSay YES! to NoSQL: A Guide on When to Ditch Relational DatabasesAdrienne Braganza Tacke · NDC Sydney 2020
• 45mNoSQL: Death to Relational DatabasesBen Scofield · RubyConf 2009
• 45mNoSQL Data Modeling for Front-end DevelopersStanimira Vlaeva · angularday 2021