# FAQ

The following are a few FAQ to provide insight into the <code class="expression">space.vars.mongodb</code> product.

## Fundamentals

### What is IONOS Cloud MongoDB?

IONOS Cloud provides a managed, cloud-native MongoDB service hosted in IONOS Cloud data centers. You can quickly deploy single-node or replica-set clusters with built-in backups and flexible, manually triggered scaling so that you can focus on your applications rather than database operations.

### Do I need to install anything to use MongoDB?

No. You can manage <code class="expression">space.vars.mongodb</code> databases in the [<mark style="color:blue;">Data Center Designer</mark>](https://docs.ionos.com/sections-test/guides/set-up-ionos-cloud/data-center-designer) or through the [<mark style="color:blue;">API</mark>](https://api.ionos.com/docs/mongodb/v1/). To connect, use a MongoDB client such as `mongosh`, `MongoDB Compass`, or an application driver.

### Which versions of MongoDB are available?

Versions 6.0 and 7.0 are supported. Select the version when you [<mark style="color:blue;">create a cluster</mark>](https://docs.ionos.com/sections-test/guides/databases/how-tos/set-up-mongodb-cluster#create-a-cluster).

### On what server instances is MongoDB offered?

**MongoDB Business** works on [<mark style="color:blue;">Cubes</mark>](https://docs.ionos.com/sections-test/guides/compute-services/cubes), and **MongoDB Enterprise** works on [<mark style="color:blue;">Dedicated Core Servers</mark>](https://docs.ionos.com/sections-test/guides/compute-services/compute-engine/dedicated-core).

### As a managed service, which services are handled by IONOS Cloud?

IONOS Cloud automates the routine, time-consuming tasks required to keep your database secure and available. The following are the services managed by IONOS Cloud:

* **Provisioning:** Supports instant deployment of database instances without manual hardware or Operating System (OS) setup.
* **Backups:** Automated recovery points to protect your data against loss.
* **Patching:** Provides seamless updates for the underlying operating system and database engine to ensure security and stability.

### What service management areas are the user responsible for within MongoDB’s managed service model?

To provide you with maximum control over your environment and costs, the following services remain under user management:

* **Scaling:** While IONOS Cloud provides the infrastructure to scale your resources upward or downward, scaling is not automatic. You are responsible for triggering vertical or horizontal scaling actions based on your specific performance requirements and manually initiating the scaling.
* **Flexibility:** You can manage costs and resource allocation precisely based on your project's lifecycle.
* **Monitoring:** We provide the data; you provide the oversight. To help you track the health of your clusters, we offer dedicated integration paths. With our integrated Monitoring as a Service (MaaS), you can [<mark style="color:blue;">Monitor MongoDB Databases</mark>](https://docs.ionos.com/cloud/tutorials/databases/mongodb/monitor-mongodb-databases).

### What is the pricing model for MongoDB?

Pricing depends on the selected [<mark style="color:blue;">Editions</mark>](https://docs.ionos.com/sections-test/guides/databases/mongodb/overview/editions) and [<mark style="color:blue;">Sizing</mark>](https://docs.ionos.com/sections-test/guides/databases/mongodb/overview/sizing) and varies by contract region. For more information, see [<mark style="color:blue;">Prices</mark>](https://docs.ionos.com/cloud/support/general-information/price-list).

## Provisioning and Configuration

### Can I modify the cluster edition after creation?

Yes. You can upgrade a cluster to **MongoDB Business** or **MongoDB Enterprise** in the [<mark style="color:blue;">DCD</mark>](https://docs.ionos.com/sections-test/guides/databases/mongodb/how-tos/update-mongodb-cluster) or through the [<mark style="color:blue;">API</mark>](https://api.ionos.com/docs/mongodb/v1/). Downgrading the instance type is not supported.

### Can the instance configuration be changed after the cluster is created?

Yes. Depending on the workload size, [<mark style="color:blue;">select the starting configuration by edition</mark>](https://docs.ionos.com/sections-test/guides/databases/overview/sizing#select-starting-configuration-by-edition). You can update the instances as needed to a higher capacity by using the guidance in [<mark style="color:blue;">Editions</mark>](https://docs.ionos.com/sections-test/guides/databases/mongodb/overview/editions).

### Which storage options are recommended for data and index storage?

Selecting the proper storage is critical for balancing performance and cost. For IONOS Cloud DBaaS, your choice depends on the database engine and your workload characteristics, such as read-heavy versus write-heavy actions.

| **Storage Type**                                                                                                                                                                | **Performance Level** | **Recommended Use Case**                                                                                                                                                                       |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [<mark style="color:blue;">SSD Premium</mark>](https://docs.ionos.com/sections-test/guides/storage-and-backup/block-storage/overview/storage-performance#ssd-storage)           | Highest (Guaranteed)  | Production Databases. Ideal for critical workloads like **MongoDB Business** and **MongoDB Enterprise** or PostgreSQL clusters that require low latency and 100% guaranteed IOPS per instance. |
| SSD Standard                                                                                                                                                                    | Balanced              | Development and staging environments. A high-speed, cost-efficient alternative to HDD for applications with moderate traffic, such as CRM systems, data analysis, or merchandise management.   |
| [<mark style="color:blue;">Hard Disk Drive (HDD)</mark>](https://docs.ionos.com/sections-test/guides/storage-and-backup/block-storage/overview/storage-performance#hdd-storage) | Cost-Optimized        | Archival and large datasets. Best for massive volumes of data with infrequent access, long-term backups, or batch workloads where latency is not a priority.                                   |

## Backup and Recovery

### What backup methods are supported?

The service creates automated daily snapshots for all deployments across all projects. Backups are retained for seven days. If you delete a database, its backups are also deleted.

### How are backups managed?

<code class="expression">space.vars.mongodb</code> clusters can have multiple snapshots, which serve as backups of the cluster's data. Each snapshot is retained for seven days, providing recovery within one week of the snapshot date. For more information, see [<mark style="color:blue;">Backups</mark>](https://docs.ionos.com/sections-test/guides/databases/overview/backup-and-recovery#backups).

### What is Point‑in-Time Recovery (PITR)?

You can create a custom snapshot for the exact `Oplog` timestamp that you choose to restore the database cluster to. This feature is available only in the **MongoDB Enterprise** edition.

## Connection Pooling

### Is connection pooling available for MongoDB?

IONOS Cloud DBaaS does not provide a separate pooler. The MongoDB drivers manage connection pooling in your application. Configure driver settings such as `maxPoolSize`, `minPoolSize`, and `waitQueueTimeout` to control connection behavior.

### How can we prevent reaching the connection limit in MongoDB?

Reuse connections and configure a reasonable pool size, such as 10–20 connections per application process, tuned to your workload. Avoid creating and tearing down connections for each request. Configure the `max_connections` using the [<mark style="color:blue;">Formula for Maximum Connections</mark>](https://docs.ionos.com/sections-test/guides/databases/overview/sizing#tune-connections-and-pools).

### Can I scale the deployment to increase MongoDB's connection capacity?

Yes. Connection capacity increases as you scale the cluster’s CPU and RAM. For guidance, see [<mark style="color:blue;">Sizing</mark>](https://docs.ionos.com/sections-test/guides/databases/overview/sizing#select-starting-configuration-by-edition). To scale resources in **MongoDB Enterprise**, contact [<mark style="color:blue;">IONOS Cloud Support</mark>](https://docs.ionos.com/cloud/support/general-information/contact-information).

## Performance and Scaling

### What is the recommended size for a production workload?

Start with a replica set of at least three nodes (one primary and two secondaries), with a minimum of 2 vCPU and 4 GB RAM for low‑to‑moderate traffic. Consider to scaling up based on observed CPU or RAM usage and latency. [<mark style="color:blue;">Monitor MongoDB Databases</mark>](https://docs.ionos.com/cloud/tutorials/databases/mongodb/monitor-mongodb-databases) to gauge the health of the MongoDB clusters.

### Can I add more read replicas to my MongoDB Enterprise cluster?

Yes. You can add up to five secondary members (a total of seven nodes) to a replica set in a **MongoDB Enterprise** cluster.

### How does sharding work?

Sharding is available only in the **MongoDB Enterprise** edition. For massive workloads that exceed the vertical limits of a standard replica set, you can use sharding. You can create a sharded cluster in the [<mark style="color:blue;">DCD</mark>](https://docs.ionos.com/sections-test/guides/databases/mongodb/how-tos/set-up-mongodb-cluster) or via the [<mark style="color:blue;">API</mark>](https://docs.ionos.com/sections-test/guides/databases/mongodb/api/v1-api/create-a-sharded-cluster). For decision guidance, see [<mark style="color:blue;">Decision matrix: When to shard?</mark>](https://docs.ionos.com/sections-test/guides/databases/overview/editions#decision-matrix-when-to-shard).

### What are the primary considerations for performance in MongoDB?

The overall MongoDB performance depends on a combination of compute, memory, storage, and workload design.

<details>

<summary><strong>Primary MongoDB Performance Considerations</strong></summary>

* **Memory or working set (for latency):** Ensure that frequently accessed data and indexes (the working set) fit in RAM. When the working set exceeds available memory and spills to disk, read latency increases significantly.
* **CPU and concurrency:** Workloads with high write volumes, aggregations, or many concurrent connections require sufficient CPU capacity. CPU saturation typically manifests as increased tail latency. Make sure to have enough processing power for concurrency and computing.
* **Storage latency and IOPS:** For disk-bound workloads, choose **SSD Premium** to achieve consistently low latency and high IOPS. It is important for write-heavy workloads, extensive indexes, and bursts.
* **Indexes and query patterns:** Correct indexing and efficient query shapes prevent collection scans and reduce random Input/Output (I/O). Poor indexes are one of the most common causes of slow queries.
* **Replication settings and topology:** Replication is primarily for availability and failover. It can improve read throughput if your application distributes reads to secondaries with appropriate read preference, but write durability settings, such as `w:majority` and cross-zone latency, can increase write latency.
* **Network placement:** Keep the application and database close together, such as in the same region or on a low-latency network. Network latency affects query response times and replication behavior.
* **Connection management:** Use driver connection pooling and avoid excessive connections, which can increase CPU or memory overhead and latency variance.
* **Scaling approach:** Scale CPU, RAM, and storage vertically first, then consider sharding when a single replica set is consistently at its limits. While it adds complexity, it enables scale-out.

</details>

**Practical recommendation:** Use SSD Premium for production, right-size RAM to fit your working set, validate indexes, and tune replication/write concern based on the desired balance of latency and durability.

## Logging and Alerts

### Where can I find the logs?

Use the cluster ID to retrieve the logs via the [<mark style="color:blue;">Get Cluster Logs API</mark>](https://api.ionos.com/docs/mongodb/v1/#tag/Logs/operation/clustersLogsGet). The log messages are collected and stored at a central location, with a 30-day retention policy.