Cloud DB for MongoDB overview
    • PDF

    Cloud DB for MongoDB overview

    • PDF

    Article Summary

    Available in VPC

    You can easily build and automatically manage MongoDB databases with Cloud DB for MongoDB. It is a fully managed cloud database service that operates stably through NAVER's optimization settings, and it automatically recovers in case of failure occurrence.

    Cloud DB for MongoDB features

    Cloud DB for MongoDB provides the following features:

    • Provision of various server types: with the provision of various server types, you can select appropriate servers for your service size, and change the server type during service
    • Provision of various service configurations: sharded cluster, replica set, and standalone configurations are provided
    • Automatic failover support (replica set): the failover feature is provided using its own primary term method in the MongoDB replica set
    • Data storage that automatically increases up to 2 TB: a default data storage of 50 GB is provided, and it is automatically increased in the units of 10 GB, up to 2 TB
    • Provision of Compass: through Compass, a GUI for MongoDB, you can search, visualize, and perform CRUD tasks for the data stored in MongoDB. You also perform analysis tasks such as indexing and document validity testing
    • Provision of BI Connector (enterprise edition): you can use the MongoDB BI Connector to use MongoDB as the data source for the BI and analysis platform. You can also combine data stored in MongoDB and data stored in other databases to conduct an integrated analysis

    About Cloud DB for MongoDB user guide

    The Cloud DB for MongoDB user guide is composed of the following topics to help you use Cloud DB for MongoDB effectively. The content that users can view in each topic is as follows:

    NAVER Cloud Platform provides a variety of related resources as well as the user guide to help customers better understand Cloud DB for MongoDB. If you are a developer or marketer in need of detailed information while you are considering adopting Cloud DB for MongoDB for your company or establishing data related policies, then please make good use of the resources below.

    Check FAQs first.

    You can get your questions answered quickly by referring to the answers in the FAQs before reading the user guide. If you haven't found the answer to your question in the following FAQs, then search the user guide for what you would like to know.

    Q. What are the tasks that need to be done in advance before creating MongoDB servers in Cloud DB for MongoDB?
    A. You need to create an application server that will communicate with the MongoDB server. However, a MongoDB server created from Cloud DB for MongoDB is currently only accessible within NAVER Cloud Platform, so the applications server must also be created inside NAVER Cloud Platform. For more information on how to create them, see Cloud DB for MongoDB scenarios and Getting started with Cloud DB for MongoDB.

    Q. Regarding the performance or operating system of MongoDB server, is there a feature that enables the configuration of thresholds and notifies the admin of the occurred events when they are exceeded?
    A. By default, Cloud DB for MongoDB provides monitoring service and event collection service for the performance and operating system of the server. In addition, you can directly set thresholds and notifications via email or SMS for occurring events by integrating with Cloud Insight. For more information on usage methods, see Monitoring and Event.

    Q. If I restart the primary MongoDB server, does failover automatically occur?
    A. If the primary is in an unresponsive status due to a failure or the user's restart command, failover automatically occurs.

    Q. Can users directly perform a failover?
    A. Users can directly perform failovers. You can reproduce a failover situation caused by a primary MongoDB server failure to check any effects on applications prior to opening the service. The server access may not be available for a certain period (minutes) during the failover process. For more information on usage methods, see Primary DB Failover of DB Server.

    Q. What is the difference between sharding and single replica set?
    A. In Single Replica Set, the client directly accesses the DB server to perform data read/write, but in Sharding, the client accesses the router server called mongos and performs necessary data read/write tasks through mongos, and transfers the results to the client. The Sharding consists of n shards, and each shard is configured in the same way as the Single Replica Set.

    Q. Can the MongoDB version be upgraded?
    A. You can upgrade into the Minor version or the Major version. Before upgrading, you must first sufficiently validate it in the test environment.


    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.