Re:We are splitting our database into Main and CI
by Gwypaas on Monday July 04, 2022 @11:01AM
(#31977781)
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.
Re:We are splitting our database into Main and CI
by kevincox on Monday July 04, 2022 @11:21AM
(#31978009)
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.
Re:We are splitting our database into Main and CI
by kennywinker on Monday July 04, 2022 @02:59PM
(#31980596)
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 :)
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.