Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex StoreDoc
  • Getting started
    • Resource relationships
    • Networking in Yandex StoreDoc
    • Quotas and limits
    • Storage in Yandex StoreDoc
    • Backups
    • Replication and fault tolerance
    • Sharding
    • Users and roles
    • Maintenance
    • Supported clients
    • Yandex StoreDoc settings
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  1. Concepts
  2. Resource relationships

Resource relationships in Yandex StoreDoc

Written by
Yandex Cloud
Updated at October 23, 2025

The main entity used in Yandex StoreDoc is a database cluster.

Each cluster consists of one or more DB hosts, which are virtual machines with DBMS servers deployed. Cluster hosts may reside in different availability zones and even different availability regions. You can learn more about Yandex Cloud availability zones in Platform overview.

  • A multi-host cluster is natively fault tolerant because its hosts can step in for one another in the primary replica capacity.

  • A single-host cluster is less costly but it does not guarantee fault tolerance.

When creating a cluster, specify:

  • Host class: VM template for deploying the cluster hosts. For a list of available host classes and their specs, see Host classes.

  • Environment: Environment where the cluster will be deployed:

    • PRODUCTION: For stable versions of your applications.
    • PRESTABLE: For testing purposes. The prestable environment is similar to the production environment and likewise covered by an SLA, but it is the first to get new features, improvements, and bug fixes. In the prestable environment, you can test new versions for compatibility with your application.

A cluster created in a folder can be accessed by all VMs connected to the same cloud network. For more information about networking, see the Virtual Private Cloud documentation.

Alert

The service can automatically access the system and diagnostic information of your databases to build monitoring charts and maintain your cluster health. The service never queries or uses the data you saved to the database.

Be mindful of what is what is controlled by the service, and what by the Yandex Cloud customer. Understanding these control zones will help you use your cloud resources effectively and avoid potential database-related problems. For more information, see Zones of control between managed database (MDB) service users and Yandex Cloud.

Was the article helpful?

Previous
Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
Next
Active host classes
© 2025 Direct Cursus Technology L.L.C.