Architecture: History and Future Illustrated by VKontakte
summary
Covers the evolution of architecture for high-load systems, tracing principles, implementation patterns and tooling choices. Uses VKontakte as a concrete case study, examining how its architecture and codebase (15 years, ~8 million lines) changed over time.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:51Highload systems defined
- 7:35Architecture vs structure
- 11:33IT industry evolution
- 24:08VKontakte in 2006
- 28:07Microservices and engines
- 31:42RPC over UDP and serialization
- 32:47Smart feed and distributed computing
- 33:53CDN and global caching
- 39:28Data storage and fault tolerance
- 42:02Code quality and KPHP
- 44:50Parallel PHP and performance
- 46:13Automation and SDK generation
- 47:43Image optimization and WebP
- 48:36Security and bot protection
- 50:03Data center optimization
- 51:28Final architecture overview
- 55:02Monitoring and incident response
- 56:48Deployment speed and TTM
- 1:00:17Future and web3 vision
- 1:03:50Open source and closing
related talks
49mFAQ on the Architecture and Operation of VKontakte
58mThe past, present and future of Architecture
54mArchitecture Is Not Nonsense
01h 13mPragmatic Architecture
13mKeynote: Role of Architecture in Building a Community
48mArchitecture: The Stuff That's Hard to Change
37mKeynote The Evolution of Evolutionary Architecture
51mArchitectural Quiz: Hack or Elegant Solution?