It’s the last three weeks of a 22-month cloud architecture project. You defined and designed a configuration that defines many cloud computing resources: databases, artificial intelligence engines, application development platforms, devops toolchains, cloudops tools, as well as security and governance.
Today you discovered that a few of the databases won’t store information in ways the applications require, the AI engine does not work with the security solution you selected, and the cost of the cloudops tools is 10 times the budgeted amount. Why did these things happen? Is it your fault?
[ Also on InfoWorld: Which multicloud architecture will win out? ]
Sometimes we catch these mistakes during the design phase of the cloud solution, no matter if it’s a net-new system or a migration from traditional platforms. Unfortunately, these and similar problems arise all the time even though the cloud architecture should minimize these types of errors.
To read this article in full, please click here
InfoWorld Cloud ComputingRead More
