Scalability Q&A
summary
Recommends PHP7, MariaDB Galera as the most common DB, and Redis for caching and sessions; TLS can terminate at load balancer or web server with tradeoffs for sticky sessions and scaling. Warns synchronous cross–data‑center replication breaks (file and DB changes must be atomically replicated), so multi‑site uses federation — example: 25,000 users split across three hosting centers works by federated sharing. Advises breaking a single instance once you approach ~100,000 users, discusses object‑store vs NFS and plans for containerized deployments.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:06Redis caching strategies
- 2:11Load balancer SSL trade-offs
- 8:30Oracle DB support
- 10:17Reference architectures
- 13:11Active Directory storage Q&A
- 14:19Nextcloud upload workflow
- 16:30Sync vs async replication
- 17:57Federation for multi-site
- 19:00Case study 25k users
- 20:45Distributed Nextcloud challenges
- 21:51Atomic file replication
- 23:52Docker container strategies
- 31:04User agent load rules
- 32:36Supported Linux distros
- 34:03Object storage vs NFS
- 37:41Performance with object stores
- 39:00Migrate object stores to NFS
- 41:11Store all in object storage
- 42:05Single instance scaling limits
- 43:08Federation unlimited scale
- 43:55Galera cluster limits
- 45:45Process isolation scaling
- 46:43Petabyte scale solutions
- 47:10Large DB setup complexity
- 48:46Redis cluster options
- 50:23Q&A
related talks
46mScaling a Collaboration Service like Nextcloud to 20 Million users
47mFrom Legacy to High-Load: Evolution of a Web Application
21mThe Multi Layered Cake of Resilience
12mScaling a Monolith, Is A Four-Letter Word
29mEvolve your web application for scale
08mWhen Worlds Collide: Frontend vs Database
56mLarge scale websites performance optimisation tricks
45mConcurrency + Distribution = Scalability + Availability (...)