News for hackers. Stuff that matters.

defnotanai

I think you confused the threads :)
Congratulations on the launch! Innovation in the Auth* space is really necessary. How do you plan on differentiating from other open source solutions, such as https://github.com/ory/kratos or https://github.com/keycloak/keycloak?
Re:Why CockroachDB and PostgreSQL Are Compatible on Thursday December 17, 2020 @01:32PM (#25458606)
You are mistaken, it is a key-value store. It just adds a ton of layers on top of the K/V to offer SQL capabilities.
Re:Why CockroachDB and PostgreSQL Are Compatible on Thursday December 17, 2020 @07:03AM (#25454811)
I am truly looking forward for CockroachDB to become the next PostgreSQL for planet-spanning database workloads. In our ecosystem we get more and more requests for CRDB integration.

Generally though, I would not say that full compatibility should even be desired. A k/v database simply works differently from a strictly relational database. There are things like shard IDs, avoiding hot spots, deciding on how to paginate data.

Going too much into "PostgreSQL" replacement will eventually hurt CRDB because too much focus will go into making legacy enterprise SQL (along the lines of https://news.ycombinator.com/item?id=25454635) work on this system. It's the forklift approach of moving to the cloud. This becomes clear when skimming through the docs:

- https://www.cockroachlabs.com/blog/how-to-choose-db-index-ke...

- https://www.cockroachlabs.com/docs/stable/performance-best-p...

- https://www.cockroachlabs.com/docs/stable/limit-offset.html

- https://www.cockroachlabs.com/docs/v20.2/selection-queries#p...

I think many of the "light SQL" patterns are really great - things like SELECT or WHERE, which e.g. DynamoDB can simply not solve without ElasticSearch. But all in all, I am very excited for CRDB to get more industry acceptance, and I think their cloud offering could also become very interesting - a competitor to Google BigTable / CloudSpanner, AWS DynamoDB or Cloud SQL.