Image alt


YDB is an open-source Distributed SQL Database that combines high availability and scalability with strong consistency and ACID transactions.

Image alt
True Elastic Scalability

Add or remove nodes to easily scale up and scale down as needed. YDB is proven to work in real production with millions of transactions per second and petabytes of data for mission-critical, real-time applications.

Image alt

YDB is designed to work in three availability zones, ensuring availability even if a node or availability zone goes offline.

Image alt
Easy to use

YDB combines strong consistency, ACID transactions, high performance queries, fast data ingest with a familiar SQL dialect and JSON API support. Works with any modern workloads: key-value, relational, JSON.

Image alt
Automatic disaster recovery

Automatic recovery after a disk, server, or even a data center fails, with minimum latency disruptions for applications.

Image alt
Available in any cloud

YDB is available for self-deployment, including Kubernetes, on-premise and cloud environments.

Image alt
Open Source

Licensed under Apache 2.0.
No risk of cloud or vendor lock-in.

YCSB performance series: YDB, CockroachDB, and YugabyteDB

YCSB is the most well-known key-value benchmark suite. We’ve prepared a performance study, comparing the key-value performance of YDB, CockroachDB, and YugabyteDB.

Read more
Image alt

Success stories

Full screen image

Market Cart

The Cart is one of the key components of any marketplace or online store.

Using YDB as a database allowed Market Cart to withstand a hundredfold increase in the load on the Cart, while observing strict guarantees for response times.

Moreover, the migration was completed by just one developer in one month.

Use cases

Dealing with suddenly increasing workloads
YDB’s elasticity allows you to quickly change the amount of resources allocated to the database, adjusting the throughput in accordance with the load. Easily increase or decrease the amount of computing resources as necessary depending on approaching increased workloads, like Black Friday or as the result of your planned marketing campaigns.
Cache with SQL interface
Low response times and throughput scalability allow YDB to be used simultaneously as an online database and a precomputed cache. SQL access significantly increases usability and enables operational analytics on data in the cache. Tour operator and travel aggregator websites, for example, can use YDB to cache flight or tour search results, as well as recalculate prices and check seasonal availability.
Jaeger Tracing
Significant comparative efficiency in computing resources and scalability make Jaeger trace recording cost-effective and easy to use. Time-tested, proven effective.

How it works

Full screen image

YDB architecture

We use commodity hardware and shared-nothing architecture, disaggregated compute and storage layers, and build a system based on logical components — tablets.

Full screen image


Similar to a file system tables could be organized into a hierarchy using directories.

Full screen image


YDB provides users with a familiar abstraction: tables. Tables must contain a primary key, the data is sorted by the primary key. Tables are automatically sharded by primary key range by size or load.

Full screen image

Split by load

The tablet will automatically split when the load increases.

Full screen image

Split by size

The tablet will automatically split when the size increases.

Full screen image

Automatic balancing

YDB evenly distributes tablets among the nodes, and moves loaded tablets from loaded nodes. CPU, Memory, Network metrics are tracked.

Full screen image

Distributed Storage Internals

We write all the code for working with block devices ourselves. The PDisk component is responsible for working with the block device. Above PDisk is the VDisk abstraction layer. There is a special component — DSProxy between the tablet (part of the table) and VDisk. DSProxy analyzes disk availability and characteristics and depending on it can make a decision to exclude the disk from work.

Full screen image


YDB writes data to 3 Availability Zones, doesn’t send requests to obviously bad disks, and continues to operate without interruption even if one AZ and a disk in another AZ are lost.

How to start


Pull the current public version of the Docker image:

docker pull

Create a working directory and start the container from it:

docker run -d --rm --name ydb-local -h localhost -p 2135:2135 -p 8765:8765 -p 2136:2136 -v $(pwd)/ydb_certs:/ydb_certs -v $(pwd)/ydb_data:/ydb_data -e YDB_DEFAULT_LOG_LEVEL=NOTICE -e GRPC_TLS_PORT=2135 -e GRPC_PORT=2136 -e MON_PORT=8765

Go to the Getting started — Self-hosted deploy — Docker in the YDB documentation to get detailed information.

YDB in a nutshell