The successful way and challenge of parsing cloud database migration

Database migration is not an overnight thing, you can't suddenly say: "Hey!" How about moving the database to the cloud today? "There is still a lot of preparation to consider before deciding on a migration." Many vendors now offer attractive cloud services, but you have to figure out what kind of products you really need. 　　

Before starting the discussion, let's think about a scenario in which cloud database migration is a viable option:

Less than the ability to manage an enterprise's internal database

It is not a central functional unit

　　As small and medium-sized enterprises need to control capital expenditure

you are using or developing a new application, you need to move the cloud as a test environment

to the cloud for disaster recovery backup, or the cloud database as a migration experiment, paving the way for later

One of the biggest benefits of cloud database migrations is availability, scalability, reliability, and cost. The cloud infrastructure is extensible and requires no fixed asset investment. If security is done well, the business is very open to cloud database migrations.

Migrating the database to the cloud while leaving the application inside the enterprise is likely to cause many problems. Two networks need to collaborate seamlessly to provide faster and better functionality. This operation needs to be done in most instances, otherwise there will be no better results than internal deployments. That's why we recommend migrating all components to the cloud, not just the database.

Evaluate database size: The size of the database determines what hardware is used, how much storage space is needed, and what instances are needed after migration. This work can be done by the internal IT team of the enterprise.

Application testing before data migration: Service providers use a number of applications to connect to the database, and these applications need to be carefully tuned. Application systems running on cloud databases also need to be able to be compatible with the cloud infrastructure and provide better performance than in-house deployment applications. The cloud data center may have a high latency problem and the application needs to be able to handle the situation. Be sure to feedback these issues to the cloud service provider so that they can be resolved in a timely manner.

Data confidentiality needs to be guaranteed: At the beginning, you may only migrate databases and applications that are not business-critical. Again, the database migration is not a matter of overnight, so a database with a lower security level can be the start of a migration.

Carefully design service level agreement (SLA) Documentation: Some applications require 99.99% uptime, so make sure downtime doesn't affect your business needs.

Ensuring scalability: Migrating a database to the most attractive part of the cloud is immediate scalability. Services and infrastructure require an ideal extension without downtime. Yes, this requires you to negotiate with your service provider to ensure that they meet your business growth plan.

Note your operating system: ensuring that the operating system runs the database is the most basic consideration, but many users tend to overlook this. For example, Oracle can run on Linux and Windows, although the implementation of the same functionality, but there will be a big difference in performance. So be sure to ensure the operating system problems in the cloud.

Garbage file consolidation can reduce costs: it is important to clean data for cloud services that charge for storage space. As the size of the database grows, your costs increase. So before migrating, be sure to remove useless junk data, thus saving a certain amount of space.

(Responsible editor: The good of the Legacy)