fomichev3000

9 ms·

1.
by fomichev3000 4y ago
The teams are approaches are different, but I need to say that internal clients are the same. Yandex is doing great things and it needs great tools.
2.
by fomichev3000 4y ago
They are totally different systems. Just they have a first letter 'Y'.
3.
by fomichev3000 4y ago
Foreign keys come at a cost, especially in distributed database. It's just a fact. If you can avoid them, it's great.
4.
by fomichev3000 4y ago
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.
5.
by fomichev3000 4y ago
We have benchmarks in our roadmap, we understand there are required.
6.
by fomichev3000 4y ago
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.
7.
by fomichev3000 4y ago
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/
8.
by fomichev3000 4y ago
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 ef
9.
by fomichev3000 4y ago
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
10.
by fomichev3000 4y ago
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
11.
by fomichev3000 4y ago
Postgres support is in progress actually.
12.
by fomichev3000 4y ago
YDB doesn't use Zookeeper. The system is built of tablets, every tablet implements distributed consensus algorithm. There are different types of tablets in the system, say SchemeShard is tablet that stores metadata, table schema for in
13.
by fomichev3000 4y ago
Each tablet gather a quorum of answers from members of so called BlobStorage group. BlobStorage group is a number of so called VDisks (virtual disk), all VDisks run on different nodes (even on different fail domain like racks, AZs). VDisk s
14.
by fomichev3000 4y ago
YDB is developed from ground up. We think about postgres compatibility layer, that's why you see 'postgres' in source code.
15.
by fomichev3000 4y ago
That's right, wire protocol is grpc. SQL dialect is called YQL. YDB doesn't have MySQL or Postgres compatibility, but we think about it.
16.
by fomichev3000 4y ago
Yes, YDB plays in this category.
17.
by fomichev3000 4y ago
YDB can work in a single AZ and such setups exist. Most of our users want to handle AZ downtime, so it's a major case.