Keynote
summary
Claims that Django defaults to Postgres because everything just works and argues for a single “post‑SQL” database that combines ACID relational features with schema‑less conveniences. Cites concrete stack components: Postgres, RabbitMQ, Elasticsearch, Redis, MongoDB, and Postgres features like hstore and JSON type plus LISTEN/NOTIFY for queues. Proposes specifics: trivial download‑run install, auto‑create tables, full transactional guarantees, easier replication/sharding. Describes this as a pragmatic roadmap, not a shipped product.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:14Why Django Chose To Recommend Postgresql
- 6:20Why I Hate Django
- 13:19Downtime Post-Mortems
- 15:19Why Am I Using Mongodb
- 18:37Post Sql Database
- 23:08Ad Hoc Queries
- 28:20No Sequel
