Scaling up and accelerating Drupal 8 with NoSQL
summary
Explains which Drupal data to move off the relational DB—key-value, state, caches; locks, paths, logging, sessions, queues—and why (reduce DB load, faster responses, easier horizontal scaling). Lists compatible stores (Redis for caches/locks/queues, MongoDB as document store, Elasticsearch for paths/search), outlines API changes and contributed modules that plug into Drupal core, and gives rules: match store to access pattern, plan durability/replication, and accept consistency tradeoffs when appropriate.
AI-written summary · about
chapters (8)
- 0:00Drupal 8 and NoSQL intro
- 5:26Why NoSQL for Drupal
- 10:35Use cases and benefits
- 17:14MongoDB demo
- 25:03Performance cache tuning
- 33:10Scalable architecture and replication
- 40:45Experience and best practices
- 48:38Q&A
related talks
01h 00mFrom Relational Databases to NoSQL
52mData storage for modern applications - Mike Lehan
42mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
34mData Storage: NoSQL Toasters and a Cloud of Kitchen Sinks
40mBeyond Relational: Data storage for modern applications
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases
43mPractical Use of NoSQL in a High-Load Project
45mSay YES! to NoSQL: A Guide on When to Ditch Relational Databases