5 Lessons from 5 Years of Building Databases at Scale by Sammy Steele

What is the fastest way to divide a group of systems engineers? Ask them to choose the best database. What actually unites most systems engineers? The idea that databases are hard.
The CAP theorem isn’t just a theory. Database engineers deal with the realities of these trade offs every day. When debugging outages, they often simultaneously encounter scaling bottlenecks, availability impacts, network outages and data corruption. When a major website goes down, there’s a good chance that databases are implicated.
Big risks come with big impact. You can remove existential risks to your company’s business by scaling out your databases. You can ensure customers keep buying your product by improving database reliability and consistency. Databases can be both a major source of cost savings and a major driver of new business new revenue.
Come explore lessons learned from 5 years of building databases at petabyte scale at Dropbox and Figma.
/ samantha-steele-b9a41aa3
Talk from Systems Distributed '24: systemsdistrib...
Join the chat at slack.tigerbee...