MongoDB on Azure¶
ObjectRocket offers the same MongoDB as a service as our traditional ObjectRocket MongoDB but running in the Microsoft Azure Cloud environment as opposed to ObjectRocket hardware. The purpose of this offering is to provide our MongoDB expertise on instances running as close as possible to the customer’s application or work-load. Customers can provision and configure these MongoDB instances via the ObjectRocket Control Panel.
Our MongoDB instances on Azure are created within an ObjectRocket owned and controlled Microsoft Azure subscription. This allows us to monitor the MongoDB instances on behalf of the customer and provide the level of support that customers expect with ObjectRocket.
Types of MongoDB instances offered on Azure¶
We currently offer MongoDB replica sets in the Microsoft Azure Cloud. Sharded and SingleDB instances are currently not supported. We have found that most customers needs can be met with a standard replica set implementation. In the future, we will be adding other types of MongoDB instances to better fit more complex MongoDB use cases.
The current replica sets consist of a primary node, a single secondary node, and an arbiter node. This differs slightly from our other ObjectRocket replica sets that contain two secondary nodes instead of the single secondary node plus arbiter configuration. These instances are still highly available and support production level workloads. They just don’t have the level of redundancy that exist with the two secondary node configurations. We will be adding the multiple secondary node configurations in the future.
Microsoft Azure Regions Supported¶
The list of Microsoft Azure Regions supported can be found in both the ObjectRocket Pricing Page and the Control Panel. We have started with the most popular regions and are continuously evaluating new regions as they become more popular. If you don’t see an Azure region that you are looking for, don’t hesitate to reach out to one of our Data Specialists.
MongoDB Versions Supported¶
We always strive to offer at least one variant of the latest MongoDB release plus one variant of the previous MongoDB release. The variant of the latest MongoDB release might be tagged as “Early Access” and our test terms would apply to these instances. We do this in order to ensure that the versions that we fully support are mature enough to be dependable for production level workloads and can be fully supported by our MongoDB experts. Once the MongoDB release evolves to a level of maturity that is dependable, we remove the “Early Access” tag.
MongoDB Backups on Azure¶
Our MongoDB instances on Azure are backed up on a daily basis and retained for 14 days. For more information on ObjectRocket MongoDB backups, see the ObjectRocket Backup and Recovery section.
Feature Differences for ObjectRocket MongoDB on Azure¶
There are a couple of feature differences between our MongoDB instances on Azure versus our traditional ObjectRocket MongoDB instances.
From time to time, customers will want to compact a MongoDB instance in order to reclaim storage space from deleted data. In our traditional ObjectRocket MongoDB instances, this can be performed by the customer or even automated. In our Azure environment, we can still perform a compaction but perform the task on behalf of the customer. If a customer wants to compact their MongoDB instance on Azure, they simply need to contact support. For more information on compactions, see our Automated Stepdown and Compaction Guide section.
We currently don’t support a statistics view of our MongoDB instances on Azure. However, we do provide customers with a space usage view and customizable space usage alert. We are always actively monitoring these instances to ensure optimal availability, reliability, and performance. If customers have concerns about the performance of their MongoDB instance(s) on Azure, they can always reach out to our Support Team for help.