When You Need to Build Your Own Database
summary
Examines when it becomes necessary for a company to implement its own database rather than use existing solutions. Discusses the practical problems and thresholds (scale, requirements, failures of off-the-shelf systems) that indicate building a custom database is justified, illustrated with developer experience from high-load systems.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:30Log system requirements
- 3:56Elastic and Loki overview
- 8:37Apache Parquet overview
- 11:51Building your own database
- 15:02HB project evolution
- 18:18SH-Nothing architecture
- 19:21Data storage optimization
- 24:06Data structures for fast search
- 27:01Exact search optimization
- 28:58Distributed search challenges
- 29:19When to build your own DB
- 31:52Q&A
related talks
42mBuilding with Purpose-Built Open Source Databases and Beyond
25mBuilding Modern Applications with Custom Databases
42mHow to Become a Great Database Specialist
45mBest Practices for Optimizing Database Projects
42mHow to Build a Database-like Application
41mHow to choose the right database for your application
35m10 things a developer should know about databases
06mWhen Database Meets DevOps
