9 engineers on Hacker News describe using CockroachDB first-hand: 5 endorse it, 2 regret it, 2 are mixed.
“We had a Django application backed by PostgreSQL, which we migrated to CockroachDB using their official backend... overall, the experience has been quite seamless.”
endorse · production · rednafi · 2025-03-14 · source ↗ · wrong label?“We switched from Cockroach (did not like the license and we had a few perf issues)”
regret · production · tluyben2 · 2022-10-20 · source ↗ · wrong label?“We have multiple CockroachDB clusters, have been for 4+ years now. We're very happy with the product... we've had quite a few issues with deleting lots of data at once”
mixed · production · 4 yr · sgtfrankieboy · 2022-09-27 · source ↗ · wrong label?“We switched to CockroachDB for some of our most heavily loaded tables a few years ago - and the scalability and operational simplicity has been great.”
endorse · production · jordanthoms · 2022-02-25 · source ↗ · wrong label?“We run almost all of our DBs - pg, cockroachdb, clickhouse ... In production under high load. Works really well.”
endorse · production · dilyevsky · 2021-07-28 · source ↗ · wrong label?“It went pretty smoothly, but you'll definetly run into issues. (Very happy overall, btw)”
mixed · production · 1 yr · latch · 2020-12-17 · source ↗ · wrong label?“some things do not perform as well in CockroachDB ... We had problems making date range queries fast with tiny amounts of data”
regret · production · andy_ppp · 2020-12-17 · source ↗ · wrong label?“I absolutely love CockroachDB in my toy projects, but am not yet feeling comfortable to commit to using it in prod.”
endorse · personal · beefsack · 2018-10-31 · source ↗ · wrong label?“I'm really impressed with it overall. The Postgres compatibility is genius in my opinion, and despite some hurdles it's been a joy to work with”
endorse · personal · smnscu · 2017-11-14 · source ↗ · wrong label?