Home PC Games Linux Windows Database Network Programming Server Mobile  
           
  Home \ Database \ How to test your MongoDB application upgrade?     - Linux common network tools: batch scanning of nmap hosting service (Linux)

- JavaScript original values and complex values (Programming)

- Redhat 5 prohibit IPv6 (Linux)

- Linux installation skynet issue summary (Linux)

- Linux SVN installation and configuration graphic tutorials (Server)

- Inherent limitations of Linux systems network security (Linux)

- Install OpenGL development environment in Fedora and Ubuntu (Linux)

- The sublime into IDE (Linux)

- Mybatis + binding Struts2: achieving user to insert and find (Programming)

- Linux POST fstab configuration file read-only variable can not be modified problem (Linux)

- Browser caching mechanism on the analysis (Linux)

- Ubuntu 12.04 64bit Install Source Insight 3.5 and create desktop icons (Linux)

- Upgrading from Fedora 20 to 21 (Linux)

- RHEL (RedHat) 6.3 using EPEL Yum source (Linux)

- Simple RPM package production (Linux)

- Linux Getting Started tutorial: Borrow Windows fonts in Ubuntu 14.10 (Linux)

- After restarting network services, DNS address failure (Linux)

- Ubuntu 14.04.02 LTS startup items erroneous writing / dev / sda1 (win 7 loader) Repair (Linux)

- C ++ pointer two third memory model (Programming)

- Use Python automatically cleared Android Engineering excess resources (Programming)

 
         
  How to test your MongoDB application upgrade?
     
  Add Date : 2018-11-21      
         
         
         
  MongoDB you have chosen as your application database. You may already have a lot of production data in your database. Now you need to make your application a major version changes. How do you ensure that applications need to test a new version of your production data and running well?

Production data is always extremely diverse, and practice your test data have more border cases, thus leading to more BUG. Not recommended export production data to the test environment, due to the policy, privacy and security issues. In other words, identification and testing BUG in a production environment is very difficult. Therefore, how to ensure that the new version of the application runs well and production data it? The following points are recommended in the MongoDirector.

1. Safety first

Our first concern is the safety and security of production data. So we do not export any production data to our bench or test environment. We have plenty of "pseudo-production" environment - this is the same as a production environment, and the environment - the same size, the same security restrictions. However, it is temporary, only for the duration of the test.

2. Cloning production MongoDB clusters

We use the "clone" feature MongoDirector, creating a real-time production data of the copy, so the cloning operation is very short no effect on the production database. This gives us a "pseudo-production" database environment, the production environment and the same characteristics - the same data, the same machine size, the same security, the same cluster configuration.



3. Run the extensive testing

We ran extensive testing to ensure that the new version of the application data and not cause problems. Once we are satisfied, we will remove the "pseudo-production 'environment.

4. upgrade your production environment

Once we are satisfied with the test results, we continue to upgrade production environments. According to the characteristics you may upgrade it to a customer a.k.a A / B and the test.

About using MongoDB test application upgrades, you have another question? You have the tools, techniques or advice you want to share it? We will be happy to hear from you.
     
         
         
         
  More:      
 
- SHELL script to use anti SSH brute force and vsftpd (Linux)
- Installation salt-minion on RHEL5 (Linux)
- Unetbootin make use U disk loading Linux system (Linux)
- Configuring DNS process under CentOS 6.5 (Server)
- Hadoop 2.7.1 Installation and Configuration under RedHat Linux 6.5 (Server)
- Ubuntu resolve sudo: source: command not found error (Linux)
- MySQL master recovery from failure using binlog (Database)
- CentOS 5.3 under broadcom NIC dual activation issues (Linux)
- Linux / Centos anti CC attack script (Linux)
- VMware virtual machine Ubuntu install arm-linux-gcc cross-compiler environment (Linux)
- CentOS 7 open ports (Linux)
- Oracle 11g R2 RAC RMAN backup script example (Database)
- Oracle to read and modify the data block process (Database)
- C # dynamic class notes --- (Dynamic) Applications (Programming)
- How VMware extend disk without rebooting the system (Linux)
- Oracle 11g creates virtual private directory RMAN-06004 ORA-00942 error handling (Database)
- Redhat 7 modify the default run level method --RHEL7 use systemd to create a symbolic link to the default runlevel (Linux)
- Oracle GoldenGate encryption (Database)
- Why I do not like the Go language style interface (ie Structural Typing) (Programming)
- These days have been tossing in the Linux under the ASP.NET 5, on the next in the other operating systems in the ASP.NET 5 or. NET applications, in order to complete the MS VM (CoreCLR) run is not far Reach, the effect of the application.

Cur
(Server)
     
           
     
  CopyRight 2002-2022 newfreesoft.com, All Rights Reserved.