CockroachDB achieves high OLTP performance of 128,000 tpmC on a 2 terabyte TPC-C dataset in size. This is 10x more TPC-C throughput than Aurora.
Geo-partitioning keeps user data close to the user, reducing latency and improving UX while archival-partitioning allows you to store data efficiently.
Since our 1.0 release, we have been hard at work making CockroachDB 2.0 the database that enables a company’s data layer to evolve with their business -- whether they are in a single datacenter or expanding around the world.
Learn which performance metrics matter, why to demand benchmark TPC-C results under serializable isolation, and how CockroachDB 2.0’s performance compares to 1.1.
With JSON support in CockroachDB, you can now use both structured and semi-structured data within the same database.
With geo-partitioning, you can control which nodes house data with row-level granularity, thereby reducing latency and improving user experience.
Why Cockroach Labs offers equity to attract engineering interns and encourage them come back to our company when they graduate.
CockroachDB takes advantage of cloud resources to let your business evolve gracefully as it grows, without requiring a re-architecture or significant migration.
Scaling a database beyond one zone is a challenge. Here's some practical advice on how to approach it.
Distributed database performance––both latency and uptime––can be dramatically improved with CDN-like multi-region deployments.