Yes: https://github.com/cockroachdb/cockroach
The parent poster was referring to CockroachDB as CRDB.
In “Follow-The-Workload” Beats the Latency-Survivability Tradeoff in CockroachDBcockroachdb
cockroach
Go2014–2026
cockroachdb / cockroach
cockroach
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
114Distinct people
170Mentions
1Explicit recommenders
32.6KGitHub stars
What to know before exploring
What it is
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
GitHub
Where it is used
- DoorDash — DoorDash runs CockroachDB as a fully abstracted internal database service for its engineering organization. DoorDash leverages it to meet availability goals at massive scale. Source
- City Storage Systems — City Storage Systems uses CockroachDB to run Tier 0 applications, migrating their order management system and user authentication platform to it. They replaced some PostgreSQL use cases with CockroachDB for these critical apps. Source
- 1 more documented example
What people are saying
Tried it before. Compatibility depends on how complicated your SQL is. There's a detailed list of supported syntax which is getting better every release but it's best for…
manigandham used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- kubernetes/kubernetes · linked in 2 of the same discussions
- moby/moby · linked in 2 of the same discussions
- pingcap/tidb · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:28:18 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year170 dated mentions
Observed mentions: 2014-05-26 11:44:43 UTC to 2026-08-11 19:04:13 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 9 | 6 | 3 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 17 | 2 | 15 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 20 | 0 | 20 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 46 | 1 | 45 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 18 | 1 | 17 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 16 | 0 | 16 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 14 | 1 | 13 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 10 | 0 | 10 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
CockroachDB is a cloud-native distributed SQL database designed to build,
scale, and manage modern, data-intensive applications.
What is CockroachDB?
Docs
Starting with Cockroach Cloud
Starting with CockroachDB
Client Drivers
Deployment
Need Help?
Contributing
Design
Comparison with Other Databases
See Also
What is CockroachDB?
CockroachDB is a distributed SQL database built on a transactional and
strongly-consistent key-value store. It scales horizontally;
survives disk, machine, rack, and even datacenter failures with
minimal latency disruption and no manual intervention; supports
strongly-consistent ACID transactions; and provides a familiar
SQL API for structuring, manipulating, and querying data.
For more details, see our product overview, FAQ or architecture document.
Docs
For guidance on installation, development, deployment, and administration, see our User Documentation.
Starting with CockroachCloud
We can run CockroachDB for you, so you don't have to run your own cluster.
See our online documentation: Quickstart with CockroachCloud
Starting with CockroachDB
Install CockroachDB: using a pre-built executable or build it from source.
Start a local cluster and connect to it via the built-in SQL client.
Learn more about CockroachDB SQL.
Use a PostgreSQL-compatible driver or ORM to build an app with CockroachDB.
Explore core features, such as data replication, automatic rebalancing, and fault tolerance and recovery.
Client Drivers
CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.
For recommended drivers that we've tested, see Install Client Drivers.
For tutorials using these drivers, as well as supported ORMs, see Example Apps.
Deployment
CockroachCloud - Steps to create a free CockroachCloud cluster on your preferred Cloud platform.
Manual - Steps to deploy a CockroachDB cluster manually on multiple machines.
Cloud - Guides for deploying CockroachDB on various cloud platforms.
Orchestration - Guides for running CockroachDB with popular open-source orchestration systems.
Need Help?
CockroachDB Community Slack - Join our slack to connect with our engineers and other users running CockroachDB.
CockroachDB Forum and Stack Overflow - Ask questions, find answers, and help other users.
Troubleshooting documentation - Learn how to troubleshoot common errors, cluster setup, and SQL query behavior.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening an issue.
Building from source
See our wiki for more details.
Contributing
We welcome your contributions! If you're looking for issues to work on, try looking at the good first issue list. We do our best to tag issues suitable for new external contributors with that label, so it's a great way to find something you can help with!
See our wiki for more details.
Engineering discussions take place on our public mailing list, cockroach-db@googlegroups.com. Also please join our Community Slack (there's a dedicated #contributors channel!) to ask questions, discuss your ideas, and connect with other contributors.
Design
For an in-depth discussion of the CockroachDB architecture, see our
Architecture
Guide.
For the original design motivation, see our design
doc.
Licensing
All versions released on or after November 18, 2024 (specifically, major version series v24.3 and later, and patch fixes for v23.1.29+, v23.2.16+, v24.1.7+, and v24.2.5+) are published under the CockroachDB Software License (CSL). Source code in a given file is licensed under the CSL and the copyright belongs to The Cockroach Authors unless otherwise noted in the file or in a LICENSE or README file located in the same or a parent directory of the file.
Comparison with Other Databases
To see how key features of CockroachDB stack up against other databases,
check out CockroachDB in Comparison.
See Also
Tech Talks (by CockroachDB founders, engineers, and customers!)
CockroachDB User Documentation
The CockroachDB Blog
Key design documents
Serializable, Lockless, Distributed: Isolation in CockroachDB
Consensus, Made Thrive
Trust, But Verify: How CockroachDB Checks Replication
Living Without Atomic Clocks
The CockroachDB Architecture Document
Read the full README on GitHubWhat Hacker News says
46 sourcesIf you are willing to give it a shot, there is currently a fork of postgrex from someone in the Elixir community! It handles some of rough edges of the incompatibility. You can find it at https://hexdocs.pm/postgrex_cdb/readme.html and the source code at https://github.com/jumpn/postgrex.
For any other issues you run into when using it, you may want to see the discussion about postgrex compatibility at https://github.com/cockroachdb/cockroach/issues/5582. If you run into different problems please do file the issue :).
I'm also an Elixir junkie, so I would also love to see ORM compatibility here! I definitely want to dedicated time to it if I can. (Disclaimer: I'm currently interning at Cockroach Labs.)
In “Follow-The-Workload” Beats the Latency-Survivability Tradeoff in CockroachDBIt's actually even in 1.0.0! We just haven't written about it previously.
The doc you found is the best resource. If you want even more detail, you can check out the original RFC: https://github.com/cockroachdb/cockroach/blob/master/docs/RF...
In “Follow-The-Workload” Beats the Latency-Survivability Tradeoff in CockroachDBYeah, it mostly happens when you have a server which runs an abnormally large task or payload, causes the heap to grow, and does it in a way that Go can't release the memory back to the OS due to heap fragmentation.
I haven't looked at this for a while but I believe it's still an issue.
https://github.com/cockroachdb/cockroach/issues/2007
https://github.com/golang/go/issues/18896
https://github.com/golang/go/issues/14045
In Erlang Garbage CollectorJSONB support is on our 2.0 roadmap and is actively under development.
Roadmap: https://github.com/cockroachdb/cockroach/wiki/Roadmap
Confirmed Development (I see you already reference this issue above):
https://github.com/cockroachdb/cockroach/issues/2969
In ACID transactions in a globally distributed databaseno, not even a JSON datatype is now supported. I cannot use a database without JSON for my use case https://github.com/cockroachdb/cockroach/issues/2969
An compatible interface is not compatibility and JSON as an example is not the biggest magic stuff inside PostgreSQL.
In ACID transactions in a globally distributed databaseThe accompanying RFC, Parallel SQL Statement Execution: https://github.com/cockroachdb/cockroach/blob/0da3da734ce6bf...
In Executing Parallel Statements to Improve PerformanceWhat "standard auth options" do you have in mind for node-to-node auth? The ones that come to my mind are even more of a pain to set up than TLS certs.
It's true that setting up a secure cluster is kind of annoying right now. But the kubernetes templates (https://github.com/cockroachdb/cockroach/tree/master/cloud/k...) do support secure mode now, and the plan is to provide more like this so it's not something that everyone has to solve by hand.
If you know or can predict the addresses or hostnames you'll be using, then it's possible to generate one cert and reuse it for multiple nodes. This isn't ideal from a security perspective since you lose the ability to revoke individual certs, but since we don't (yet) support CRLs/OCSP it's not much of a loss.
Adding an option to skip hostname checks for node certs might make this less of a pain (i
Read the rest
t would then be trivial to share one cert for all nodes if that's what you want to do). We'll consider that and see if it compromises any important security properties.
It's on our roadmap and is actively being worked on right now. Should be available for version 1.2.
See:
https://github.com/cockroachdb/cockroach/blob/master/docs/RF...
In CockroachDB 1.1 Released: Production Made EasyI’m currently a developer at Cockroach working on interleaved tables.
If by multi tenancy you mean sharding by a particular column (or set of columns) to groups of nodes, interleaved tables are probably not what you’re looking for. Table partitioning is currently on the roadmap and you can find the RFC here https://github.com/cockroachdb/cockroach/blob/master/docs/RF....
In CockroachDB 1.1 Released: Production Made EasyVery interesting. What do you think about CockroachDB (https://github.com/cockroachdb/cockroach)? Is that serious enough to the challenge, from outside Google?
In Designing Data-Intensive ApplicationsHi all--My name is Andy and I'm a PM here at Cockroach labs. We are currently working through partitioning as a key feature of our 1.2 release scheduled for April 2018. Our solution can be found at this RFC (https://github.com/cockroachdb/cockroach/pull/18683). One thing to note, we don't require you to define your partitions up front. We'd love to get your feedback on this feature--please feel free to comment on the RFC or reach out to me directly at andy@cockroachlabs.com.
In PostgreSQL 10 ReleasedIn that I would be curious on RocksDB vs LMDB. There was an issue about this but it didn't progress: https://github.com/cockroachdb/cockroach/issues/14#issuecomm...
For some reason(s) nobody is using LMDB on distributed dbs (only know actordb). While for single-nodes there are many cases that have switched and been better.
In Avoid Vendor Lock-In Risk with Multi-Cloud DeploymentsBesides the blog, you can find interesting stuff in the source repo, in the technotes and RFC dirs:
https://github.com/cockroachdb/cockroach/tree/master/docs/te...
https://github.com/cockroachdb/cockroach/tree/master/docs/RF...
There's also a bunch of technical tech-talks linked from our company's website:
https://www.cockroachlabs.com/community/tech-talks/
In Avoid Vendor Lock-In Risk with Multi-Cloud DeploymentsI have to bring this up again: NewSQL. There are quite a few new choices out there, Google Spanner, Cockroachdb(https://github.com/cockroachdb/cockroach), TiDB (https://github.com/pingcap/tidb). All of them are very easy to scale while maintaining the ACID transactions.
In Why SQL is beating NoSQL, and what this means for the future of dataShowing the 15 most recent of 46 sources. Enable JavaScript to search and browse every indexed mention.