📝MongoDB overview:-

📝MongoDB space usage:-

✒️Calculating space for MongoDB plans:-

On the ObjectRocket MongoDB platform, a plan represents the maximum amount of data you can store on a MongoDB instance without taking any action. When building a MongoDB instance for the first time, you’re required to choose a size in incrementing blocks, such as 5 GB, 20 GB, 50 GB, or others. Because you’ll know exactly how the capacity increases as you grow, this size selection makes it easy to plan out scaling in advance.


If the MongoDB instance is running on WiredTiger, two values are used from the dbStats output, dbStats.storageSize (dss) and dbStats.indexSize (dis). Using these values is necessary because WiredTiger stores data and indexes in separate files.


MMAPv1 stores data and indexes on the same files, so the only important output is dbStats.fileSize. While MMAPv1 logs both dbStats.storageSize and dbStats.indexSize, this information is only useful in roughly determining the level of fragmentation within the MongoDB instance.

✒️What is not calculated

ObjectRocket fully manages MongoDB for you, including the pieces that create storage amplification like replication, journaling, namespace file, and ObjectRocket administrative databases. The following space calculations aren’t necessary:

  • Journal size
  • Namespace size


We are happy to announce that MongoDB version 4.2 has passed our tests and is generally available on the ObjectRocket platform.

🖊️What’s New in MongoDB 4.2

You can get the full list of what is available in the MongoDB 4.2 release notes. Here are some of the updates and changes we wanted to highlight:-


➡️Increased Security

MongoDB 4.2 adds TLS options that are meant to replace SSL options (SSL is deprecated to 4.2). Additionally, client-side field level encryption is introduced that helps you to protect sensitive data. Read more on security improvements here.

➡️Bug Fixes

As with every major version, 4.2 fixes bugs that aren’t backported. Put simply, this means that some bugs affecting older versions are fixed in 4.2 but never backported for different reasons in previous versions, like 4.0 and 3.6.

➡️General Enhancements

Aggregation improvements: MongoDB 4.2 supports on-demand materialized views. Using the $merge operator allows users to save the aggregation output to a collection. $merge operator provides more flexibility compared to the $out operator and can help you enhance your security model.

📝Why Use MongoDB?

MongoDB is a document, NoSQL database that offers ease of implementation while combining performance, high availability, and automatic scaling. MongoDB, compared to MySQL, enables users to modernize existing relational workloads by addressing the requirements of new applications while supporting features like multi-document ACID transactions.

🖊️Benefits of ObjectRocket for MongoDB

🖊️24/7 Fanatical Support
by MongoDB Experts

Monitoring & Alerts

🖊️Proactive MongoDB
Database Administration

MongoDB Sharding

✒️ObjectRocket for MongoDB Features

Sharded and replica MongoDB instances are offered in 3 member replica sets for data redundancy and fault tolerance. Sharded instances consist of MongoS servers, config servers, and the shards themselves. All instances are capable of running the latest MongoDB version and enable SSL encryption connection along with an approved IP whitelist configured by the customer.

▶️Tools & Integrations

  • API Access
  • Restful API
  • Slow Query Detection
  • Automated Compaction
  • New Relic Integration
  • Profiling Limiter

▶️Custom and Advanced Configurations

  • 3 Node Replica Sets
  • Sharded Clusters
  • Percona Server for Enterprise Workloads
  • Single Database

▶️Security: RocketSecure Database Access

  • Integrated Firewalls
  • SSL Encryption
  • Encryption for Data at Rest
  • Audit Log Access
  • LDAP Integration
  • Delayed Replica Node


MongoDB versions 3.6, 4.0, and 4.2 instances in AWS and GCP are now available via our Private DBaaS offering. Rather than using shared infrastructure, Private DBaaS allows you to get a completely dedicated DBaaS cluster in almost any AWS or GCP region that you can use to host any and all of our hosted database services.



Nothing is impossible