The Architecture of Stack Overflow for Teams
summary
Describes the design and launch of Stack Overflow for Teams, focusing on handling private data in a multi-tenant system that was originally designed as “default public.” Covers the architectural decisions, scalability solutions, and security measures used to enable private, multi-tenant usage of the Stack Overflow platform.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:38Stack Overflow overview
- 7:14Infrastructure and performance
- 10:28Scalable monolith
- 13:15Stack Overflow for Teams origin
- 17:28Multi-tenant architecture
- 20:38Data modeling challenges
- 23:05Per-team schema solution
- 27:00Provisioning and scalability
- 29:06Elasticsearch indexes
- 30:30Redis challenges
- 31:57Data security and isolation
- 33:43Secure routing for teams
- 37:16Project lessons learned
- 38:56Pre-launch stress tests
- 39:21Security beyond hackers
related talks
41mRe-architecting Stack Overflow
33mHigh Performance Architecture Of Stack Overflow
47mHigh perf architecture at Stack Overflow
33mHow we do Architecture at Okta
46mArchitecture for Cross-Functional Teams
46mAdaptive Socio-Technical Systems with Architecture for Flow
54mIncrementally Rebuilding Stack Overflow's Monolith
13mTech Symphony: Orchestrating Best Practices Across Diverse Techn. Stacks
