CockroachDB

Limitations

• Strict clock synchronization via NTP is required; physical clock skew exceeding the configured limit causes nodes to crash intentionally to preserve data consistency.
• Single-key read and write operations exhibit higher baseline latency than standalone PostgreSQL because Raft consensus and transaction intents require network hops.
• Applications must implement client-side transaction retry handling to resolve serialization conflict errors (error code 40001) generated during concurrent write contention.
• Compatibility omits native PostgreSQL extensions, procedural triggers, deferrable constraints, and connection pub-sub commands like LISTEN and NOTIFY, requiring changefeeds for streaming data.

Who should use it

• DevOps engineers who manage high-availability infrastructure: the cluster handles node failures and zero-downtime rolling upgrades automatically.
• Distributed backend developers building multi-region applications: the database delivers standard SQL syntax alongside serializable guarantees across separate geographic locations.
• Platform teams bound by strict data sovereignty mandates: self-hosting preserves full administrative control over storage volumes, private networks, and encryption keys.

FAQ

CockroachDB vs CockroachDB Dedicated — which deployment model should a team choose? CockroachDB Dedicated fits teams wanting Cockroach Labs to manage cloud infrastructure, patches, and automated backups on AWS or Google Cloud. Self-hosted CockroachDB is better for teams operating private Kubernetes clusters or requiring absolute data governance.

Is self-hosted CockroachDB free for production use? CockroachDB source code uses the BSL-1.0 license, allowing free internal production use for organizations below specific revenue and cluster scale thresholds defined by Cockroach Labs. Larger enterprises or companies offering database hosting services require a commercial license.

Can CockroachDB serve as a drop-in replacement for PostgreSQL? It connects via standard PostgreSQL drivers and supports typical SQL schemas, but it lacks support for native extensions, triggers, or procedural languages. Applications also must handle distributed transaction retries.

Verdict

CockroachDB is an exceptional database for engineering teams requiring multi-master distributed SQL and continuous cluster availability, provided application services can tolerate distributed transaction retries and slightly higher single-key latency. Active development with frequent GitHub commits ensures regular engine refinements and expanding PostgreSQL compatibility, while its BSL-1.0 license permits internal enterprise deployments but restricts unauthorized commercial hosting. For organizations seeking distributed resilience on private infrastructure without cloud lock-in, it provides an established foundation.