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

Resource relationships in Managed Service for MongoDB

Written by
Yandex Cloud
Updated at October 14, 2024

The main entity used in Managed Service for MongoDB 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 apps.
    • PRESTABLE: For testing purposes. The prestable environment is similar to the production environment and likewise covered by the SLA, but it is the first to get new functionalities, improvements, and bug fixes. In the prestable environment, you can test compatibility of new versions 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.

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.