True Elastic Scalability
Easy to use
Automatic disaster recovery
Available in any cloud
No risk of cloud or vendor lock-in.
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.
Dealing with suddenly increasing workloadsYDB’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 interfaceLow 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 TracingSignificant comparative efficiency in computing resources and scalability make Jaeger trace recording cost-effective and easy to use. Time-tested, proven effective.
How it works
We use commodity hardware and shared-nothing architecture, disaggregated compute and storage layers, and build a system based on logical components — tablets.
Similar to a file system tables could be organized into a hierarchy using directories.
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.
Split by load
The tablet will automatically split when the load increases.
Split by size
The tablet will automatically split when the size increases.
YDB evenly distributes tablets among the nodes, and moves loaded tablets from loaded nodes. CPU, Memory, Network metrics are tracked.
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.
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 cr.yandex/yc/yandex-docker-local-ydb:latest
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 cr.yandex/yc/yandex-docker-local-ydb:latest
Go to the Getting started — Self-hosted deploy — Docker in the YDB documentation to get detailed information.