Hacker News Reader

Comment by herrkanin | Hacker News Reader

Which databases are the main contenders, that you were referring to?

Disclaimer: I now work at https://www.yugabyte.com/yugabytedb/, I joined because I liked their approach and think it has a lot of merit.

But there are also https://www.cockroachlabs.com/product/, https://github.com/pingcap/tidb and https://ydb.tech/ which each has promise.

There is definitely lots of progress to make in this space. From what I have seen they are all significantly slower on a single node and are not as battle-hardened. But I think with time we will have a few really nice options to pick from.

You also have FoundationDB, which seems quite battle hardened with Snowflake's, Apple's and Datadog's adoption.

Only provides a quite barebones Key Value interface to play around with though, so not anywhere near a drop in replacement to your traditional SQL database.

https://www.foundationdb.org/

I didn't mention FoundationDB since it isn't relational. I think the relational model with automatic indexes and query optimization is a huge benefit. That being said of all of the options mentioned it does seem like the most battle-tested. I would love to see a relational layer built on top of it and see how that turns out.

I believe CloudKit is built on FoundationDB

> CloudKit allows you to store your data as CKRecord objects, and relationships between those objects as CKRecord.Reference associations.

https://developer.apple.com/documentation/cloudkit/designing...

I’m not a database guy so idk if that meets the technical definition of “relational” but it is a database with relationships :)

Clickhouse is nice, though it does require you to give up some pretty significant capabilities shared by most traditional SQL DBs.

Aurora, alloydb, spanner

Reply on news.ycombinator.com