Anyone know a difference between Yugabyte and YDB? Both seem to be in the OLTP space.
I actually thought Yugabyte renamed itself YDB. :(
They are totally different systems. Just they have a first letter 'Y'.
Readit Newsfomichev3000 commented on YDB – An open-source Distributed SQL Database ydb.tech... · Posted by u/diimdeep
fomichev3000 commented on YDB – An open-source Distributed SQL Database ydb.tech... · Posted by u/diimdeep
If that comparison table is right about "no foreign keys," that's a showstopper for me. :(
Back to looking at Couchbase, Yugabase, or Citus for my distributed SQL.
Foreign keys come at a cost, especially in distributed database. It's just a fact. If you can avoid them, it's great.
fomichev3000 commented on YDB – An open-source Distributed SQL Database ydb.tech... · Posted by u/diimdeep
here is a table that compares YDB to postgress
https://db-engines.com/en/system/PostgreSQL%3BYandex+Databas...
I think they wanted to have a DB that is better tuned to distributed systems. Still don't know, why they do an SQL like query language called YQL (what would that mean in practical terms? Could a common ORM framework like JPA deal with the YQL query language ?)
The table is a bit outdated, we are going to fix it.
To be honest, YQL is a very popular language in our company, it is successfully used for more than 7 years, but I agree that outside people want to see more standard SQL dialect.
fomichev3000 commented on YDB – An open-source Distributed SQL Database ydb.tech... · Posted by u/diimdeep
Are there any notable differences or benchmarks between YDB vs CockroachDB, Spanner, or Yugabyte?
We have benchmarks in our roadmap, we understand there are required.
fomichev3000 commented on YDB – An open-source Distributed SQL Database ydb.tech... · Posted by u/diimdeep
What's the core ordering mechanism behind the serializability for arbitrary distributed transactions? This would be something like TrueTime in Spanner or FoundationDB's GRV/commit proxies.
The core tx ordering mechanism is inspired by Calvin deterministic transactions mechanism. We have some differences, like we have a distributed tx coordinator that allow us to scale number of transactions in flight.
fomichev3000 commented on YDB – An open-source Distributed SQL Database ydb.tech... · Posted by u/diimdeep
Which consensus algorithm? I don't see raft in the codebase
We have consensus protocol over shared log.
Some details you can find in a power point presentation at this page https://2019.hydraconf.com/2019/talks/muxomfgqembsb3st7i3ci/
fomichev3000 commented on YDB – An open-source Distributed SQL Database ydb.tech... · Posted by u/diimdeep
I don't see any plans for support of Windows Server. Do you know of any plans for it? Since it still has about 75% of the on-prem server market
Thanks for pointing this out. I think it's possible, most of the code is cross platform, we used to build YDB on Windows, so it should not be a problem. I suppose we need to improve a layer that works with storage devices to make it effective, for now it should be very naive implementation.
fomichev3000 commented on YDB – An open-source Distributed SQL Database ydb.tech... · Posted by u/diimdeep
It seems they are doing the same thing they did with ClickHouse in the OLAP space but this time in the OLTP space.
Yes, you can think this way. But I need to add, that YDB is also a platform for developing distributed systems that store data. YDB provides a scalable and replicated storage with low latency, a conception of a tablet (that is also used in many systems) that implements distributed consensus. These building blocks are used for persistent queue implementation, block store, KV-tablets. These blocks are hard to develop and they are very good when you need to build something new or optimal for a specific problem. OLTP is an example of such a problem. But yes, we were building YDB to support OLTP workload initially.
fomichev3000 commented on YDB – An open-source Distributed SQL Database ydb.tech... · Posted by u/diimdeep
imo having had to deal with oracle sql, teradata sql, mssql and mysql, postgres as a dialect is such a sane and consistent experience.
Also the ecosystem... The official docs basically solve your problems without much fuss, you don't have to rely on horrible vendor-specific forums.
While you have a good point, I need to say that traditional databases and distributed databases differ in some points. For instance in YDB you can connect to any node of a database, it means that you need some kind of balancing (server side or client side). I'm not talking about SQL dialect right now, but rather how you connect to database and how you handle connection losses or node overloads. YDB SDKs have client side balancing feature to distribute load evenly across database nodes.
Asking because I pretty much like Clickhouse.