Presented by:

A78ae3da0e9f634a55be5f6da12e0f06

Jim Walker

Cockroach Labs

Jim is a developer who has spent a large part of his career helping people understand complex, emerging technology. He is passionate about distributed systems, data and open source technologies. He is also a startup-aholic and loves building apps and new communities. He is currently the VP of Product Marketing at Cockroach Labs and has helped build companies like Hortonworks and CoreOS. Jim has a BS from the University of Illinois at Chicago, a MS from Carnegie Mellon University.

35d17dddd69bd244051fc57140a511a7

Chris Casano

Cockroach Labs

Sharding is how most of us scale Postgres. It works, however, it is not without its challenges. What key should we shard on? How big will my shards need to be? How will sharding affect performance? What application-level mods will need to happen? What happens if we need to re-shard the database?

Automating the sharding process seems right. We should be able to define a shard and let the db take care of the underlying segmentation and movement of data.

CockroachDB is wire-compatible with PostgreSQL and automates the sharding process. If you want to scale, you simply spin up a node, point it at the cluster and the database takes care of rebalancing and moving data. You can scale on the fly and even reshard while in production without downtime or loss of data.

In this webinar, we will speak through how CockroachDB delivers this effortless scale, covering: Primary keys in Cockroach - the “key” to sharding RAFT, range partitions and the architecture that delivers scale Automating data placement for latency and resilience Re-shard in production without downtime All while speaking SQL

Date:
2020 June 25 10:00
Duration:
1 h
Room:
Online
Conference:
Postgres Webinar Series
Language:
Track:
Case Study
Difficulty:
Requires Registration:
Yes (Registered: 201)