As organizations migrate to the cloud, they need a cloud-native, relational database to help them move all their applications to this new environment.
For CockroachDB 19.1, we improved the cost-based optimizer with automatic collection of table statistics.
Geo-partition to keep user data close to users and to decrease latency in your applications all over the world.
Today, we’re excited to release CockroachDB 19.1. With this release, we enhanced distributed SQL capabilities, and expanded upon enterprise-grade features for security and data integration.
From NoSQL to NewSQL to a new breed of database: Distributed SQL.
Why are Go executable programs larger than expected? We visualized the CockroachDB binaries using tree maps to find out.
Disasters happen. (Most) outages shouldn't. So why do mission-critical services, like banking, still go dark in 2019?
Bose's cloud engineering team spoke with Elastic and Cockroach users at last week's Elasticsearch community meetup.
Achieving compliance with data localization regulations can be prohibitively expensive (depending on how your database is architected). It's important to evaluate where compliance is worth the effort and where it's not.
Compliance with data localization laws is difficult and expensive. It’s particularly expensive with a monolithic DB. This blog outlines the yellow brick road towards compliance and flexibility for shifts in the data protection tectonic plates.