Choosing a MongoDB Deployment
- Updated2025-02-19
- 2 minute(s) read
Choosing a MongoDB Deployment
Most of the SystemLink services use MongoDB as the primary database. You can use MongoDB on the same server hosting SystemLink or set up a remote MongoDB instance.
Use the following table to choose the MongoDB deployment that best suits your
use case.
Deployment | Description | When to Use |
---|---|---|
Single node with defaults | This is the default installation where you have one server that hosts both SystemLink and MongoDB Community Edition. |
Note If you
increase the index cache, you can use this deployment
with up to 25 managed nodes.
|
Multi-node with standalone MongoDB instance | You have two different servers hosting SystemLink and MongoDB. | When the MongoDB Windows service is consuming enough CPU, memory, and disk space to impact the operation of SystemLink services. |
Multi-node with MongoDB replica sets | You have one server hosting SystemLink and three or more servers hosting MongoDB. NI Recommends the configuration for all production deployments. |
|
Multi-node with MongoDB Atlas | You have one server hosting SystemLink and are connecting to a MongoDB Atlas cluster. |
|
Note NI recommends using MongoDB replica sets or MongoDB Atlas for all
production deployments.