We’ve hinted at it throughout this series, but now we’re going to say it explicitly: To get the most out of the cloud you should be combining solutions. At the very least, you should be thinking more flexibly than “AWS is for engineering, Azure is for IT.”
Does Your Engineering Department Need Azure?
In many organizations, some processes will be a better fit for AWS, while others will be more at home with Azure. And again, the standard “engineering on AWS, IT on Azure” division is not the best guide to this process. For example, corporate IT applications and workloads often fit more comfortably on AWS. More dynamic processes, like public-facing web services that don’t require scaling and aren’t integrated into Microsoft run on AWS without incident.
The Challenge of Multi-Cloud Solutions
The challenge, of course, is that neither of these platforms are free. You must carefully evaluate whether or not a multi-cloud solution is cost effective.
There’s also not a consistent set of code for each. Managing all of that code and the scripts that go along with it is a labor-intensive task. Figuring out whether your team is up to the task is an important consideration. Architecture also presents a significant challenge.