Retiring MongoDB Classic on Compose

Published

The end of MongoDB Classic at Compose has begun.

The process that will see the winding down of MongoDB Classic has begun. Our second implementation of Hosted MongoDB, originally dubbed Elastic Deployments way back in 2014 is now officially heading towards its end of life.

Its successor, Compose for MongoDB, has shown itself to be a more secure and reliable offering. It is the core offering for MongoDB on the Compose platform. By contrast, MongoDB Classic has seen less development and we feel it unfair on customers to keep the older MongoDB Classic available.

The schedule has been set:

In a little over 30 days time, as of August 20th, 2018, unless you already have a MongoDB Classic database, you will no longer be able to provision a new MongoDB Classic deployment.

Existing users will then have twelve months to plan and execute their migration to, for example, Compose's current MongoDB or IBM Cloud Compose for MongoDB. We are working on a tool to make that migration as simple as possible and plan to have news in the coming months.

At the end of the twelve months after new provisioning of MongoDB Classic has been stopped, we will begin the process of shutting down all MongoDB Classic databases.

attribution Bess-Hamiti

Default avatar The default author avatar
The Compose Team The fine team of people at Compose have brought this article to you through teamwork. Remember, teamwork makes the dreamwork. Love this article? Head over to The Compose Team’s author page to keep reading.

Conquer the Data Layer

Spend your time developing apps, not managing databases.