Database is like a car. You have classic cars that everyone loves, and now they cost 20 times what they did in the 1970s. Also, you have new cars that don’t have the same sex appeal but works much better than cars built 30 years ago; They are faster, achieve better mileage and have the latest technology.
Many data sets are being moved to the cloud and now data sets are forced to move workloads and data must consider their options.
The first option is to simply transfer your enterprise database license to a public cloud provider. It is called bringing your own license (BYOL). This is the least resistant path, because all you are doing is transferring the original data to database A to another database on another server platform, this time stored on the public cloud. plus.
However, that is not the cheapest way to go. You can pay annually for your enterprise database and it may not have the features, functions and performance of some cloud-based database options, available on request. (based on usage).
Although your specific requirements may vary, in general, the original cloud database is a better way to move data to the cloud. The downside is that you will need to download and retrieve data for a new private storage model. Moreover, you will have to change the database access application.
I suppose this is that you may need to refactor the application to take advantage of the original services on the cloud, so you can also refactor the original database on the new cloud. This can increase frustration for some people, but the end result is that applications and databases work better, providing more features and functions, lower usage costs and Built purpose for your specific use case.
This is one of the times when switching to the cloud means you will have the right choices in front of you, but they will have higher initial costs. However, I suspect that if you don’t do what is best now, you may have to move your data twice, at even higher costs.