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

InfoWorld Cloud Computing

IDG Contributor Network: How to migrate IT to AWS in record time with the extended EC2

One of the problems with today’s IT transformation is the lack of reliable engineering approaches adapted to fast-paced business environments. Much more than we think, it prevents a productive dialogue between consultants and clients.

While CIOs expect big pictures that demonstrate changes and benefits, certain consultants continue to address IT transformation through the specifics of the solutions they plan to implement. 

IT transformation design patterns are the answers, I’ve been using them for 15 years to help Fortune 500 companies get value from the transformation of their IT.

The extended EC2 design pattern I developed to facilitate application and even data center migration to the Amazon Web Services (AWS) cloud environment is a case in point.

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

CIO Cloud Computing

The right way to migrate to the cloud

Migration to the cloud is a journey that presents new challenges. Along the way, you need to consider more details than you first thought, and there are many paths available to move applications, but not all of them are right for your migration.

The first step for every migration is to define the types of workloads you need to migrate. This does not mean each application, but the patterns of processing that the applications comprise. You must determine what those patterns are, then place existing workloads in each pattern.

For example, let’s say these three patterns of workloads exist in your enterprise:

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

InfoWorld Cloud Computing