Choosing the right database
summary
Compares relational vs document database modeling using a web CV app example where an ORM-generated relational schema causes slow reads due to 12 joins; recommends representing each CV as a single JSON document in a document store (examples: Postgres for relational, MongoDB for documents, Elasticsearch for search). Reviews trade-offs in transactions, indexing, scaling and recovery across systems (mentions Cassandra and column-family/TS stores like Influx/Prometheus), and explains migration and backup implications for choosing a database.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:24Comment on m'a appris à l'école ?
- 0:47Comment on m'a contacté ?
- 1:13Bien choisir sa base de données
- 2:12Les bases relationnelles
- 3:05Les documents
- 6:07Sommaire
- 6:36Recherche par identifiant
- 12:08Gestion des transactions
- 15:47Structure fixe ou flexible ?
- 20:51Performances
- 23:50Disponibilité, escalabilité
- 30:56Les HOPS
- 35:13Récapitulatif
- 39:40Questions
related talks
01h 00mThe Modern Database Debate: Documents, Tables, or Documents in Tables?
46mFrom Tables to Documents -- Changing Your Database Mindset
19mRelational or Non-Relational? Choosing the Best Database for the Task
01h 00mFrom Relational Databases to NoSQL
41mHow to choose the right database for your application- 19mRelational or Non-Relational? Choosing the Best Database for the Task
42mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
55mData Modeling in a Non-Relational World