Fix your databases now as you migrate to the cloud

If you have lame databases in your on-premises systems, don’t move them to the cloud. They’ll still be lame databases.

As thousands of enterprises move their application workloads and data to the cloud, too many move whatever they have, include their lame databases. It’s easy to just lift and shift them you’ll find the popular on-premises databases also available in the cloud. So you end up with the same limitations, just running somewhere new.

Don’t do that. Instead, reevaluate the type, and the brand of databases you’re using as part of your cloud migration.

Use the cloud migration effort to vastly improve your data management and data use capabilities. For example, consider moving from SQL or relational databases to NoSQL or object-based databases, which maybe a better fit for your patterns of data use.

To read this article in full or to leave a comment, please click here

If you have lame databases in your on-premises systems, don’t move them to the cloud. They’ll still be lame databases.

As thousands of enterprises move their application workloads and data to the cloud, too many move whatever they have, include their lame databases. It’s easy to just lift and shift them you’ll find the popular on-premises databases also available in the cloud. So you end up with the same limitations, just running somewhere new.

Don’t do that. Instead, reevaluate the type, and the brand of databases you’re using as part of your cloud migration.

Use the cloud migration effort to vastly improve your data management and data use capabilities. For example, consider moving from SQL or relational databases to NoSQL or object-based databases, which maybe a better fit for your patterns of data use.

To read this article in full or to leave a comment, please click here