 Live from Las Vegas, it's theCUBE, covering the AWS Accenture Executive Summit, brought to you by Accenture. Welcome back everyone to theCUBE's live coverage of the AWS Executive Summit. I'm your host, Rebecca Knight. We have two guests for this segment. We have Tawny Creffield, she is the managing director, communications, media and high tech at Accenture, and Adam Burden, chief software engineer at Accenture. Thanks so much for coming on theCUBE. Happy to be here. So we are talking today about the future of platforms, and Adam, I'm going to start with you to just sort of give our viewers a lay of the land here. It's been a few years since platform development really hit the scene. So it's been an interesting space for us as well. When I talk about what's happening in this area, I like to break it up into the how, the now and the wow. And the how is really what is created or enabled by these platforms. It really is abstracting away the complexity, this plumbing and difficult parts of building software bespoke in systems. And it's making that complexity sort of disappear so that the real effort is expended upon building systems and enabling business value. And when we talk about how that has changed the way that we look at systems integration and development, it's actually enabling this thing that we call the renaissance of custom to a degree. And that's really kind of the how. And in the now side of this, it's interesting, when we first started tracking this space, these platform areas, I want to say it was close to eight years ago, we actually called it the Helen of Troy effect, right? So we had the face that launched a thousand ships. There literally were a thousand platforms out there floating around in the ocean. And some of them had a lot of sailors on it and a few of them were just dingy's. But now what we're seeing happen is this consolidation of platforms and it's taken a couple of different forms. Sometimes you've got something like one of these really popular open source platforms like Cloud Foundry. And it's actually becoming sort of an OEM product inside of a lot of other platforms. So you see Cloud Foundry now inside of things like SAP Cloud Platform, for example. So it's popping up in surprising places. Plus you can also use the community version. But that consolidation is now sort of channeling down the number of platform options, environments that are available to build things on top of. So that's a very interesting development that's happening right now. And the wow is what's happening tomorrow. And I tell you, I see some remarkable things on the horizon working with our ecosystem partners that really will change the way that clients, businesses, the enterprises, especially the ones that have ambition to be the high performers of tomorrow, how they're going to enable business applications and systems for their customers. And we talk about things like low code and no code platforms. Imagine a scenario where you can talk to an intelligent agent and describe the system that you want to build and the scaffolding for that is created for you. So really remarkable advances and leaps forward coming ahead in the platform space. And when I think about the how and how we've gotten here, the now and the wow, it's just an exciting time to be working in this area. So what are some of the primary benefits? As you said, you're talking to clients who want to become the high performers of tomorrow. What kind of successes are you seeing? So I would really group that into probably two things, Rebecca. I think the first one is around agility. One of the things I like to say is that the pace of technology change will never be as slow again as it is today. And it's sort of a daunting thing. Which is mind-boggling in itself. It's kind of daunting. And being here at AWS re-invent, we're about to be bombarded with an unprecedented number of new product and capability announcements over the next couple of days. It's hard to absorb all of these things and hard to be able to take advantage of them. And for our businesses and our clients that we work with, they're looking for agility. And that's one of the key benefits that you get out of being a part of one of these platforms. It allows them to be more responsive to the market and they can do it in a way which is really, it's enabling them to deliver solutions faster and better than ever before. And think about the competitive threats that they're facing, right? With cloud technologies like AWS, we've really democratized a lot of compute, like never before. Because of that, it's a lot easier for a startup or even a company in an adjacent industry to come in and say, I'm going to start doing things in this space. I'm going to sell roofing products and I'm a car manufacturer, for example. And when you have things like that happening and it's so easy for competitors to get in and be disruptive, it's really important the business that you can move quickly. And these platforms enable just that. So agility is clearly one of them. And then the other one is around innovation. If you think about how hard it would be for my colleague here, Tani and I, if we were going to build a new customer service system that had a natural language processing and a virtual agent technology in it, and we were going to try and build this in our own data center, right? Stand up the infrastructure, set up all the services, be able to do this, train the models ourselves. We're talking about something that could take months or years even, just to get to the point where we're ready to start building. Yet today, with a lot of these platforms, you don't have to do any of that. You can start tomorrow and it's all as a service, it's on tap, it's on demand. And if you're taking, if you're going to be one of these high performers of tomorrow, using it as an innovation platform is absolutely a key component of the success of the future for that business, no doubt. Tani, I want to bring you in here a little bit to this conversation. So talk to me about a specific example of a platform that Accenture has been working on. So I'd like to highlight Open AP, it's just a great example of what Adam was talking about, where it was a consortium of media giants that came together to build a new platform really to disrupt the broadcast TV industry and find a way of doing targeted advertising more effectively. So broadcast TV is usually done based on gender and age demographics, that's it. They want to find a way of really being more specific targeting veterans or people who want to buy trucks or whatever. And they did this by wanting to create a cloud platform that would become the marketplace between agencies and the broadcasters. And they, you know, but because it's a consortium, there's no infrastructure, there's no starting point. It was from thin air, from scratch. And they, because of the broadcast industry timelines, they wanted to do the entire, from idea to launch in five months. And we couldn't have done that if, to Adam's point, if we had to, you know, create, you know, put in servers and all that stuff. We were able to do all of that because we were able to leverage AWS as a baseline and get started with the development almost immediately. So talk a little bit more about this Open AP. So it's a consortium of media companies and sort of looking at their digital competitors with a little bit of envy here of, wow, you can slice and dice your target customers so finely and you know exactly who they are, what they want to buy, what their consumer proclivities are. And they want it to be able to do the same. Yeah, so there's a lot of analytics that they wanted to leverage and do it in a way that there was a standard across the different media companies because they realized that, you know, the biggest threat was coming from digital, not from each other. So they kind of got together and said, hey, let's find a way of doing this more frictionless, make it more seamless. We can have a lot of the data and the analytics behind it so that you could target, like I said, you know, veterans or whatever. And by doing so, they're able to create that marketplace. But to do that, we had to really make it easy to use. We had to build, you know, custom UIs back to exactly the renaissance of custom. It was there's nothing out there in the marketplace that would do this. They were the first ones in there to really disrupt the marketplace. So it was, you know, custom UIs, you know, APIs, the whole, you know, that whole set of capabilities that needed to be done for the consortium. So Adam, in terms of these platform services, talk a little bit about what you have learned so far and sort of the best practices that have emerged, the nuggets of wisdom. Thanks, Rebecca. I love it when people ask me that question because I have two things that I think are really important to keep in mind with that. One of them is that if you're building green field applications, right, it's actually time to throw the baby out with the bathwater. And it's a bit hard sometimes because there's a lot of inertia in enterprises about how you do things and how things have been done. And a lot of times they can be quite conservative too about their approaches. So for example, if you're going to use a platform, but what you're going to do on that platform is you're going to stay using waterfall development techniques. You're going to have releases every three or six months or something. That's just, that's not going to meet your business's expectations anymore. It goes back to what I was saying a few minutes ago about the speed of change in technology. It's just not going to keep up with what potentially competitors are going to do. So you have to throw out a lot of those, that baggage that you've carried with you for a long time. A great example I like to talk about in this space is actually site reliability engineering. This is a pattern for architecture, solving architecture problems that really has become quite popular in the last couple of years. And what it allows you to do is to, is to release software a lot faster, but you have more circuit breakers inside of your applications that allow it to gracefully degrade if there's some sort of defect or problem that happens so that your customers, your business partners, your employees, they don't see an outage. What they see is a slightly degraded service. They don't get something where it says, you know, at 404, site not available, they get a slightly degraded service. And if you follow those patterns well, you can deliver software a lot faster with higher degrees of quality, but you have the comfort and assurance that it's going to do that. That actually helps you get over some of the cultural barriers as well. Well, those cultural barriers, and I'm interested in your experience at OpenAP too, in terms, what you just described is exactly right. Is that there is this inertia, there is this enterprises, we've been doing things our way for a long time and they're not broke. So can you talk about the challenges of having to overcome that? Yeah. You know, I think that with the consortium, we had a little bit of an advantage in that it was pure green field. And we, you know, the consortium was very specific about the first pain points they wanted to focus on and really wanted to build it as an MVP, you know, minimal viable product, not trying to do everything at once. And that was really key to us. So once we really knew what they wanted to do, we put in all of the dev sec ops agile practices so that we could move fast. We did, you know, automated testing and test harnesses and built in the security, the scalability, the performance from the beginning so that we weren't halfway down the road and then had to try to bolt that stuff in later. And just we really all had a vision of what we needed to get to and we were able to leverage all of the modern technology practices to get there. I'm not going to say it wasn't hard. Five months was kind of crazy, especially because it had to be ready to launch and go live. And in fact, we had a beta day which was industry experts coming to test it, hands-on demo at Paramount Studios in California. Like no pressure, four months after we started and it was awesome. But it was because we had the vision and then we had all the new tooling and the technologies and the ability to build in some of that stuff from the beginning, which I think in a green field scenario really helped us. Adam, final word. In terms of next year's AWS executive summit, what are we going to talk about? We were already talking about the future platforms. What is going to be next year's buzz? I really think that there's going to be this momentum towards something called Go Native. And this is going to be, so there's a lot of enterprises that are taking advantage of cloud today, but they're using it as compute storage and power and the real value for them is going to be unlocked by taking advantage of the native services that are there. And when we think about things that AWS reinvent, it has announced in the last couple of years and I'm sure it's going to come up this year. Think about things like Lambda and Aurora and others. These are native cloud services that taking advantage of those and not just sort of bringing the other components of your older architecture with you, that will really unleash a new era of innovation for your company and you'll be able to do things faster and better and you'll have even better outcomes for your clients, your customers and business partners than you would otherwise. So, Go Native. It's going to be the next year. Go Native, okay, you heard it here first folks. Adam, Tawny, thank you so much for coming on theCUBE, it was great talking to you. I'm Rebecca Knight, we will have more of theCUBE's live coverage of the AWS Executive Summit coming up in just a little bit.