YDB – an open source distributed SQL database(ydb.tech)
ydb.tech
YDB – an open source distributed SQL database
https://ydb.tech/
5 comments
Appears to be another Yandex spinoff like ClickHouse, so it's probably reasonable to assume that it has the same properties: well-built, fast, and (initially, at least) slightly under-documented ;)
There're some proofs, check the https://blog.ydb.tech/ for comparison against CockroachDB and YugabyteDB.
Same here. The only clue I found are the following two lines in the Q/A section: "What consistency model does YDB use? To read data, YDB uses a model of strict data consistency."
There is some info at https://ydb.tech/docs/en/concepts/
To say it is light on details is to say nothing…
But big claims require much more and the claims are huge (ie. It is a perfect DBMS)
But big claims require much more and the claims are huge (ie. It is a perfect DBMS)
Well it is an in-house tool that just got opensourced, so it is natural that docs and other materials are lacking. There are videos from C++/HighLoad meetups that shed light on internals, but mostly in russian as of now. Give it time.
I'm looking forward to ydb having a better day 1/2 operations.
They have a kubernetes operator, but I don't know if they had great backup logistics. Also, iirc, the volume expansion at the time was not supported.
My GitHub issue on the matter
https://github.com/ydb-platform/ydb-kubernetes-operator/issu...
They have a kubernetes operator, but I don't know if they had great backup logistics. Also, iirc, the volume expansion at the time was not supported.
My GitHub issue on the matter
https://github.com/ydb-platform/ydb-kubernetes-operator/issu...
This is a good source for features that may/may not already be existing.
https://github.com/ydb-platform/ydb/blob/main/ROADMAP.md
https://github.com/ydb-platform/ydb/blob/main/ROADMAP.md
there was some conversation from a while back: https://news.ycombinator.com/item?id=31081272 (April 19, 2022 — 403 points, 318 comments)
>Interesting, the separate compute and storage tiers is another system going that direction which I think is becoming almost the standard at this point, especially for "cloud-native" things designed to run on k8s. From what I can tell (it isn't very explicit on this point) they are avoiding a distributed consensus at the storage layer and instead relying on a single writer/multiple reader model with the single writer being enforced by assignment of the tablets in the compute tier, with the tablet being responsible for writing to multiple storage nodes for durability? (But I might be wrong)
Hmmm, 4D around the 90's/early 2000's also keep the data and code separated in 2 different files. They maybe still do, but haven't touched it in a while. Tech is more and more like fashion, if you wait around long enough it will come back. ;-)
Hmmm, 4D around the 90's/early 2000's also keep the data and code separated in 2 different files. They maybe still do, but haven't touched it in a while. Tech is more and more like fashion, if you wait around long enough it will come back. ;-)
Databases have had their storage and compute together for as long as i remember.
It's changing now, though, in a good way.
TiDB, YDB, SurrealDB, singlestore, etc is changing that.
I am looking forward to a seamless way to move data from hot to cold. For PG, timescale does that, but only for their cloud offering.
It's changing now, though, in a good way.
TiDB, YDB, SurrealDB, singlestore, etc is changing that.
I am looking forward to a seamless way to move data from hot to cold. For PG, timescale does that, but only for their cloud offering.
Ydb vs tidb?
Right now tidb. ydb has a few operational challenges that i can see. TiDB was solid during the time i gave it a try.
It does not build any confidence as the topic of distributed highly available and scalable databases is inherently difficult and solutions are full of trade offs.