Just Say No to Multi-cloud
Transcript
[Music] hey how's it going to keep Townsend from the CTO visor come with a bit of a rent of a CTO dose I'm going to try and make this be as beneficial as possible tie two things together I put out a Twitter request acting for people to give me ideas and then long silence that I tweeted a interaction I have for CTO some months ago who wanted to use multi cloud to basically save money houma Schmidt asked me to do something on compliance and governance and
I think this is I think a great topic to meld into I think a source of angst with me in the community and as I talk to organizations about their cloud strategy one consistent theme that I get is that there's organizations that's anxious to do multi cloud not exactly sure why they want to do multi cloud but they are certain that they want to do multi cloud one of those reasons is to save money you know what full-stop no don't don't attempt to spend up a
huge tent team of people your vendors etc trying to save one cloud cost by spreading workloads across there's way too many complexities to deal with just to save cost focused on your single cloud provider or separate cloud providers and driving those costs down and those individual cloud providers which gives us to the point of why people are pursuing multi-cloud strategies first off everyone has multi cloud whether you're using salesforce.com workforce type SAS offerings ATP SAS in a combination of ayahs or platform-as-a-service from Microsoft Azure GCP
or AWS we all have multi-cloud the frustration is I think Enterprise architects CTO CEOs experienced when they look at multi cloud as that is just their cloud environment is just overwhelming they have these things that have grown organically whether it's within their own organizations or outside and they just don't have a handle on the overall governance of cloud you may have a very mature data center practice in which governance is is is locking step with the business you've over the years you've develop a process for
change management change control orders auditors can come in audit your environment and you have a handle on the environment we lose a bit of control when we go out to the cloudy initially just one cloud I've shared the story in the past of how Netflix went down doing a Christmas Eve due to poor not necessary poor control meant on configuration management change management but because of a Mitch mechs and configuration management change management Netflix made a change AWS made a change those two changes weren't coordinated
and as a result Netflix at outage enterprises we don't have the scale of Netflix we experienced these very same things especially as we deal with multi cloud there are drivers for multi cloud for example you have machine learning you want to do on a data set it TCP offers GPUs just platforms - that are just better for doing machine learning AWS is leading the way when it comes to functions as a service if you're building applications that land themselves for functions that could literally and this
is an exception to the rule that can literally save you thousands of dollars a month on an application if you built it using functions and the triggers and and capabilities of a lambda then these are two very good reasons to go one with eight us and another with with GCP but on whole I think organizations need to first understand the governance around a single cloud before they go adopting a multi cloud strategy and biting off more than they can chew they need to first understand how
they're going to take their governance model from their data center and bring that into the public cloud two completely different infrastructures two different types of capabilities we can't be in the public cloud to our policies and wheels so we have to work around the public cloud providers so bringing our governance to from the data center into the cloud simply won't work unless we're doing a VM C of VMware cloud on AWS and even still that we lose a bit of control VMware is gonna upgrade and
update the version of VMware cloud on AWS the underlying vSphere version much faster than we do on Prem we have to just work around that so I'm not a fan of the concept of enterprises embracing multi cloud before they've mastered a single cloud master a single cloud as there's projects that's out and doing their thing in multiple clouds you can offer them best level of service but have a opinionated view on the cloud that you support from a CTO Enterprise Architect perspective this is the preferred
architecture this the set of services that we support here's how we implement these services on a single cloud understand the frictions that it creates in your governance address those governance issues and then expand out from there when it comes to multi cloud this is you know pretty different than some advice you get from storage vendors who talk through you know you should have a multi cloud strategy for accessing storage from different cloud providers yes that's true technically you should have you should think about that stuff
and you should make purchasing decisions based on that but from a practical implementation of your cloud and cloud strategy start with one cloud expand out from there you'll find you have plenty of work and you'll be a lot more successful there's a lot of people that disagree with me and you've already voiced your opinion some of you on Twitter but you know come back and let's have the conversation I'm at CTL advisor on Twitter you can find me on LinkedIn and well as these CTO dose
videos you can search for the hats hashtag hashtag CTO dose no spaces talk to you next CTO dose until then follow me on the web the CTO visor com
