Databases are like automobiles. You have the classic cars that everyone looks back on fondly, and now they cost 20 times what they did back in the 1970s. Also, you have the newest cars that don't have the exact same sex appeal but function far better than cars built 30 years ago; they are faster, get better mileage, and have the latest technology.
Many data sets are being relocated to the cloud, and now those charged with transferring the workloads and data must consider their alternatives.
The first choice is to simply move your business database permit to the public cloud supplier. It's called"bring your license" (BYOL). This is the path of least resistance, considering that all you're doing is moving data native to database A to database A on a different host stage, this time hosted from the public cloud.
However, it's not the cheapest way to go. You're likely paying out the nose annually to your enterprise database, and it probably does not have the characteristics, functions, and performance of a cloud-native database options, that have on-demand (usage-based) pricing.
Even though your specific requirements may vary, generally speaking, cloud-native databases are a better way to synchronize data into the cloud. The downside is that you'll need to load and recast the information for a brand new native storage model. In addition, you'll have to modify the applications that access the database.
My take on this is that you'd likely need to refactor the software anyway to leverage cloud-native services, so you might as well refactor to get a brand new cloud-native database as well. This may increase the frustration for a few, but the end results are applications and databases which function better, offer more features and functions, cost less to use, and are purpose-built for your specific use case.
This is one of those times when moving into the cloud means you'll have the right options in front of you, but they'll come in a higher initial cost. However, I guess that if you do not do what's best today, you'll likely have to migrate your information twice, in a much greater price.
Let's not do that.