If you test your MongoDB application upgrade?

If you test your MongoDB application upgrade?

Original English text:

Http://blog.mongodirector.com/how-do-you-test-your-mongodb-application-upgrades/

You have chosen MongoDB as your application database. You may already have a lot of production data in your database. Now you need to make a major version change to your application. How do you test to make sure the new version of the application and your production data work well?

Production data is always extremely diverse, and your test data and practices have more boundary cases, resulting in more BUG. Exporting production data to the test environment is not recommended due to policy, privacy and security issues. In other words, it is quite difficult to identify and test BUG in a production environment. So how do you ensure that the new version of the application and production data work well? The following points are recommended by us at MongoDirector.

1. Safety first

Our first concern is security and the security of production data. Therefore, we will never export any production data to our workbench or test environment. We have a "pseudo-production" environment-- this is the same environment as the production environment-- the same size and the same safety restrictions. However, it is temporary and is only used during testing.

two。 Clone production environment MongoDB cluster

We used the "clone" feature of MongoDirector to create an instant copy of the production data, so the clone operation had no impact on the production database for a short time. This gives us a "pseudo-production" database environment with the same characteristics as the production environment-the same data, the same machine size, the same security, the same cluster configuration, etc.

3. Run extensive tests

We run extensive tests to ensure that the new version of the application does not cause problems with the data. Once we are satisfied, we delete the "pseudo-production" environment.

4. Upgrade the production environment

Once we are satisfied with the test results, we continue to upgrade the production environment application. Depending on the feature, you may also upgrade it to test for a customer a.k.an AploB.

Do you have any other questions about testing upgrades for applications that use MongoDB? Do you have any tools, techniques or suggestions you want to share? We are glad to hear from you.