MongoDB Documentation, Release 3.0.4 MongoDB provides different levels of write concern to better address the specific needs of applications. Clients may adjust write concern to ensure that the most important operations persist successfully to an entire MongoDB deployment. For other less critical operations, clients can adjust the write concern to ensure faster performance rather than ensure persistence to the entire deployment. See the Write Concern (page 78) document for more information about choosing an appropriate write concern level for your deployment. Use Trusted Networking Environments Always run MongoDB in a trusted environment , with network rules that prevent access from all unknown machines, systems, and networks. As with any sensitive system that is dependent on network access, your MongoDB deployment should only be accessible to specific systems that require access, such as application servers, monitoring services, and other MongoDB components. Note: By default, authorization (page 324) is not enabled, and mongod assumes a trusted environment. Enable authorization mode as needed. For more information on authentication mechanisms supported in MongoDB as well as authorization in MongoDB, see Authentication (page 320) and Authorization (page 324). For additional information and considerations on security, refer to the documents in the Security Section (page 317), specifically: For Windows users, consider the Windows Server Technet Article on TCP Configuration 61 when deploying MongoDB on Windows. Disable HTTP Interfaces MongoDB provides interfaces to check the status of the server and, optionally, run queries on it, over HTTP. In production environments, disable the HTTP interfaces. See HTTP Status Interface (page 329). Manage Connection Pool Sizes To avoid overloading the connection resources of a single mongod or mongos instance, ensure that clients maintain reasonable connection pool sizes. Adjust the connection pool size to suit your use case, beginning at 110-115% of the typical number of concurrent database requests. The connPoolStats command returns information regarding the number of open connections to the current database for mongos and mongod instances in sharded clusters. See also Allocate Sufficient RAM and CPU (page 200). MongoDB is designed specifically with commodity hardware in mind and has few hardware requirements or limita- tions. MongoDB’s core components run on little-endian hardware, primarily x86/x86_64 processors. Client libraries (i.e. drivers) can run on big or little endian systems. 5.1. Administration Concepts 199 $^{61}$http://technet.microsoft.com/en-us/library/dd349797.aspx Hardware Considerations • Security Checklist (page 431) • Configuration Options (page 327) • Firewalls (page 328) • Network Security Tutorials (page 335) Networking