RoachFest videos
Customer talks
Resilience: A question of mindset, culture, and partnershipsThree years of CockroachDB on Kubernetes: Trials and triumphs at City Storage SystemsDoorDash’s Journey from Aurora Postgres to CockroachDBSurviving 100x scaling events: Picking the right technologies earlyMulti-cloud essentials: How we operate CockroachDB at Form3Yes, you can reduce TCO while meeting strict regulatory requirementsPlanning for scale: CockroachDB @ MaterializeHow Shopmonkey built a faster, more scalable, geo-distributed version of our application on CockroachDBMigrating from chaos into consensusHow CockroachDB is helping us do the impossible with global cloud storagePlanning for scale: CockroachDB @ Materialize
Member of Technical Staff Materialize Parker Timmerman
Materialize put a streaming engine in a database so teams can build real-time data products without the cost, complexity, and development time of stream processing. To deliver on Materialize’s speed and correctness guarantees, we needed a strongly consistent and scalable metadata store. CockroachDB fit the bill. First, we'll walk through how CockroachDB allows Materialize to deliver on these correctness guarantees, then we'll discuss how we've leveraged CockroachDB's scalability to keep Materialize fast as we've grown our user base. We'll dive into some technical details like how using CockroachDB immediately sidestepped performance bottlenecks in vanilla PostgreSQL, and how we further tuned our data layout and access patterns for CockroachDB's architecture. Overall, CockroachDB solves hard distributed systems problems, so we can focus on our killer feature of incremental computation.