This documentation describes the a9s MongoDB service. a9s MongoDB enables on-demand provisioning of VM-based, dedicated MongoDB servers and clusters. Developers can create instances of a MongoDB server or cluster using Apps Manager or the Cloud Foundry Command Line interface (cf CLI) and bind these instances to an application. Depending on your service plan, a service instance may be associated with a single, dedicated VM or a set of VMs consisting of multiple VMs containing a MongoDB replica set cluster.
When you run the cf CLI
create-service a9s-mongodb command, BOSH creates dedicated
VMs for this service instance. This allows the best possible bad neighborhood protection.
MongoDB service instance provisioning, including VM orchestration, is entirely automated. This enables service instances to be highly isolated and shielded by infrastructure virtualization mechanisms.
Due to the on-demand provisioning on VMs, only existing service instances allocate infrastructure resources. These resources are released when service instances are destroyed. Using on-demand provisioning the number of service instances is not limited by design.
Distributed across multiple infrastructure availability zones, clustered data service plans enable short failover times and are resilient against failures of individual infrastructure hosts or entire availability zones.
The current version of a9s MongoDB includes the following key features:
|On-Demand Service Instance Provisioning||a9s MongoDB deploys MongoDB instances automatically. Developers can provision a single-VM MongoDB server or a multi-VM MongoDB Replica Set using a single command.|
|Service Instance Isolation||Each MongoDB server runs on a dedicated VM to ensure bad neighborhood protection in order to be aligned with enterprise security requirements.|
a9s MongoDB uses Cloud Foundry security groups to prevent network connections being established by unauthorized applications.
|High Availability||a9s MongoDB ensures high-availability using MongoDB Replica Sets.|
The Consul-based internal DNS system ensures that the connected application always connects to a working node.
|Smoke Tests||a9s MongoDB contains a post-deploy smoke tests errand that runs a series of basic test against your installation to ensure that it is configured properly.|
|Service Instance Capacity Upgrade||Cloud Foundry Service Plan updates allow upgrades to the RAM, CPU and storage capacity for your MongoDB instances.|
|Logging and Monitoring||Each MongoDB service instance provides log messages and MongoDB-specific metrics to one or more |
|Deployment Updater||This errand automatically updates the stemcell and all provisioned a9s MongoDB service instances to their lastest version.|
|Backup Manager||The Backup Manager does regular backup of your instances and offers endpoints to backup instantly and restore backups.|
|Service Guard||The Service Guard creates Cloud Foundry security groups for your service instance VMs.|
When the IP address of a service instance changes, the guard updates the security group.
MongoDB Inc. has changed the license of the MongoDB code base from AGPL to SSPL. This licensing change affects all MongoDB releases from MongoDB Inc. after 16th of October 2018. anynines has so far not published a release containing code under the new licence, however we are likely ship SSPL MongoDB versions in future. The SSPL licence may or may not impact on your MongoDB usage. If you are running MongoDB for users inside your organisation then this is fine as before. However if you are offering MongoDB as a service to 3rd parties (for example via a Public PaaS) then you will need a commercial agreement with MongoDB Inc. You can find out more about the SSPL on here: Server Side Public License FAQ. If you believe your use case will be affected by the SSPL please get in touch with anynines and we will help you art a conversation with MongoDB Inc. about commercial licensing. Releases containing SSPL code will be clearly labeled and we will communicate the changes as far as possible ahead of time.