Amazon, Microsoft, Forty Years discussed on Software Engineering Daily


Could move workloads. Sure there was the dream of kuban. Attis multi cloud single. Api workloads across multiple clouds. No one's really doing that yet. And if you are like please do a conference. I think everyone would want to see it. The fact that people don't even do conference talks about that solution kind of proves to me. No one's even really doing it because it's just a hard problem but even if you could easily do that easily run a workload in any cloud anywhere. You still have a data problem right. You have a data a network problem. And that's why places like. Aws they make the data so easy the data in s. three as that central world around all these other services because the more you put in three the less likely you're galil aws. I almost believe that that's one of their signals of knowing you know people are locked in. There is like the more data you had like. If you're gonna move its are you gonna move expedites out of like unlikely right. You're just gonna leave your workloads there. Some people do and they can. It's atypical usually. It's one of those that were data goes as we need it but most of it's never accessed again. Think of how many pictures people take and store and various services that are using s threes. Their storage for that and never actually access those things again. Like how many pictures taken where you take the picture you access at once and then it sits there forever and rods. Because you don't need to know what your dinner receipt was back in two thousand fourteen. But they can't get rid of it because you kind of actually might need to present that at some point in case of an audit or something. So how do you solve those problems. Well you wind up finding ways to do this at scale massively. So much of that is almost certainly dead stock slash data. That will never be touched again. But god help them. If one day it goes on available. Yeah i mean that was the dream of the startup. I was that was sony. Email archiving and like you're never going to probably need that email again until you need it and when you need it like it's probably because you have lawyers asking you for it right so having a place that you can put an object like an email or bundle of emails and not have to think about it for a really long time is so compelling like who wouldn't want something like that just dump your data here and maybe i'll do something with it later and navy. Some proc manager comes along is like oh god we can do some analytics all this data we have and because it's all there right now you can do stuff with it. I'm really looking forward to seeing what the future cloud holds. The challenges though is that there are over fifty billion dollars a year now in run rate and bat is an awful lot of revenue pouring in there but they got there by reaching out specifically to developers and infrastructure people to wind up driving cloud adoption. The next fifty billion is not gonna come from those folks. It's gonna come from a lot of the blue chip enterprise style companies that are migrating in various directions. And that's a challenge that historically aws has done a relatively poor job of learning to speak to those businesses in ways that resonate talking to the it ops person who is not going to learn cloud formation. They're going to do things in the console for example is a bit of a stretch for them in many cultural respects. You can't do bottom up adoption the same way anymore because it turns out neither developers nor operations folks in. It are empowered to sign a fifty million dollar. Cloud deal the second time because the first time they did. They were fired and prosecuted. Yeah i mean amazon. They're not known for that. They're not known for being able to speak to. We'll call like the old guard enterprise. There's a lot of data centers still out there. There's a lot of workloads that are still in those data centers and you ve. Companies like oracle and microsoft. That are odyssey this way. Better at telling that story to those people everyone thinks. I'm kidding when i say this about microsoft but the honest truth is is that they have forty years of experience apologizing for software failures and that is exactly what you need to do in the cloud because things break all the time and at scale that is what happens and you never get away from that. So you best be able to articulate that in a language and a context that you're angry customers understand and appreciate and microsoft is the undisputed expert in that space. Yeah i mean. Microsoft has the advantage in the enterprise. We've been in the enterprise for you know thirty plus years right. It's so easy for them. They're already there with exchange server and all other components that tie into it with active directory. They know how to talk to those. It folks and they're already involved in those engagements whereas amazon amazon is not selling an email service to these companies. They're not selling domain controllers services and exchange services and file. Services and share point microsoft. Already they're already have their foot in the door. So feel like amazon has a big hill to climb in order to even meet them at their level right. They have to go way above to get to those. You know old guard. It ops folks that are dealing with exchange servers and share point service shares. And things like that and sure amazon has a whole slew of things that you could use. That can kind of replicate that service. But like if. I'm an exchange admin i kind of want hosted exchange. I'm going to go to microsoft to get my hosted exchange. I wouldn't even think of amazon for that service. Even though they could probably provide a pretty similar offering and one of the biggest problems now is there fifteen different services that.

Coming up next