>>Hello everyone. Thank you, add appreciating the studio. We're here at the cube here in cloud city telco DRS Cloud city. I'm Jeffrey Day Volonte. We're here for the next three days. Wall to wall live coverage. It's a physical event with a virtual program. It's hybrid. We're here with Daniel Royston, the Ceo of telco D. R. And the acting Ceo Toby, which is announced today. Great >>to see you. It's awesome to see you guys. >>Awesome to see how you doing, how you >>Feeling? I'm feeling congratulations. Right. 101 days ago, I didn't even think this doesn't exist. Right. And we got in contact with you guys and we said we knew there was always going to be a big virtual component and we invited you guys and here we are together. It's insane. >>Well we did the preview videos, but we're kind of walking through and document in the early stages. It all came together beautifully spectacular For the folks watching behind us is the most spectacular build out clouds. It's an ecosystem open concept. It feels like the Apple store meets paradise. Of course. We got the cube here in the set and we got the studio with all the command and control of adam there. So I gotta ask you with the connected keynotes going on right now. The connected world. Yeah. It's connected. We all know that everyone knows that what's, what's different now real quick before we get into the program, what's going on? >>Yeah. I think a big part of my messages and advocating it's more than just the network, Right? And I think telcos forever have relied on. That's all it is. That's what it's about. And I'm like, nope, you guys got to start focusing on your subscribers, right? And so the over the top players keep coming in and siphoning away their revenue and it's time for them to start focusing on us, right and making experience great. And I think that's what this is all about. >>So we're gonna get the news but I want to toss it to Katie. The roving reporter is going to give it a detail on how it all came together. So Katie take it away. >>Mhm We're here in Barcelona and so excited to be back in this beautiful city over at the convention center. The team is working hard putting the finishing touches to tell Cody are amazing cloud city booth at MwC Barcelona 2021. I'm sure you know the story of how this all came together as one of the biggest vendors Erickson pulled out of M. W. C. With just over 100 days until the start of the event. When this happened last year, it kicked off a tidal wave of departures and MwC was called off this year. We all wondered if MWC was going to be cancelled again and that's when Daniel Royston Ceo of Telco D. R. And Tito G swooped in and took over the booth all 6000 square meters of it. The plan turn the booth into cloud city, the epicenter of public cloud innovation at MWC crews have been working around the clock. Over 100 and 50 people have been on this construction site for over three weeks with covid testing every day to prevent outbreaks during the build and in 100 days, it's become just that Cloud city has over 30 vendors presenting over 70 demos with 24 private meeting areas. Cloud City Live is a virtual showcase and live broadcast studio featuring 50 guests from cloud Thought leaders around the world. They have telepresence robots for a more personalized experience and the Cloud city quest game with a chance to win more than $100,000 to gain access to live streams of our nightly concerts with rosario flores and rock legend Jon bon Jovi. And don't forget to visit cloud city dot telco D R dot com to join in on the fun Daniel Royston and Nacho Gomez, founder and Ceo of one of the key vendors in the construction of the booth gave us a behind the scenes tour of the booth. >>Nacho. We did it. Yeah, we did. It can't even touch because of Covid. Yeah, but look what we did. But right, 100 days ago I called and I said I'm taking over the Ericsson booth. What did you think? I know you were crazy but just a little bit crazy, realized that you were mortgages than I thought. So at the very, at the very beginning I thought, yeah, she's crazy. But then I couldn't sleep that night. But the next uh then I realized that it was a very good it's a great idea. Yeah super smart. So yeah we're gonna show everyone toward the booth. Yeah let's go. Let's go. Okay So how do we build such an amazing, beautiful building now? So this is we've made building inside a book. So it was very hard to find a glassful of facade. The roof is around 24 tones. Yeah so it's crazy crazy but we made it work and it's totally amazing. Yeah. Do you want to go to tragedy life? Do let's go. Okay so here we are Cloud city live. I know we're producing a whole live streaming tv show. We always knew because of covid that not everyone will be able to come to Mwc as we wanted to make sure that people can learn about the public cloud. So over here we have the keynote stage, we're gonna have awesome speakers talking all throughout M. W. C. People from AWS Microsoft, google vendors companies. So really really great content. And then over there we have the cube interviewing people again 15 minute segments, live streaming but also available on demand. And you can find all of this content on cloud city. Tell Cody are calm and it's available for anyone to you. Well, a lot of content. And what about the roberts? I never get them out. Come on. We remember 100 days ago we were locked down. So we came up with the idea of having robots for the people who cannot attend in person. I know right. We always knew that there was gonna be a big virtual component to MWC this year. So we bought 100 telepresence robots. It's a great way to have a more personal experience inside the boot. Just sign up for one on cloud city dot telco D r dot com and you can control it yourself. Right? So today we have Nikki with us, who's dialing in from the Philippines in Manila? Hello, Nicky. Hi there, how are you? I were great. Can you show us a twirl all gaining on us? Super cool. Yeah, it is. What an experience. So Nikki robots are not the only cool thing we have in cloud city. We also have super awesome concert. We have rosario flores on monday. Who's a latin grammy award winner. We have Jon bon Jovi, Jon bon Jovi on Tuesday, can't be changing telephone that a little bit of rock n roll and that's Tuesday. And on Wednesday we have DJ official, it's going to be a super party. Now if you play our cloud city quest on cloud city telco D R dot com you can participate in a live streaming concert and so I know a lot of people out there have been a lockdown. Haven't been able to be going to concerts. Things from austin texas, which is the live music capital of the world, How to have music. It would be so exciting is gonna be great. I'm getting hungry. Why don't we go to the restaurant? Let's go eat. Let's go. Yeah, Here is our awesome restaurant. I know it's called Cloud nine. Right? It's a place to come and sit down and relax now. Barcelona is known for its great food and I'm a foodie. So we had to have a restaurant. Should we go check out my secret bar? Let's go. Mhm. Yeah, here >>thanks to a R. And thank you Nacho if you're watching this at home, I'm so sorry you can't join us in person. However, let's not forget this is a hybrid event meaning we're bringing all the public cloud action right to you wherever in the world you might be. This includes the Pact cloud city live program. We've partnered with the cube Silicon angle Media's live streaming video studio to make sure that all of the keynotes, panel discussions, demos, case studies interviews and way more are available on demand so you can watch them whenever and wherever you want or you can live stream and enjoy all things cloud city as and when they happen. So for those of you not able to join us in, Barcelona, be sure to log in to cloud city live and catch all the action and don't miss the awesome concert Tuesday night with Jon bon Jovi available for free. If you participate in our cloud city quest game, I'll be here throughout MWc bringing you reports and updates. Stay >>tuned. Yeah. >>Mhm. Okay, we're back here on the cube on the floor at mobile world congress in cloud city telco DRS clouds. They were here with D. R. Of telco, D R. Danielle Rice and great to see you back, we're back. So the keynotes going on connected world, the big news here, I'll see the open shift that's happening is going open. Open ran, it's been a big thing. Open ran alliance. You're starting to see the industry come together around this clear mandate that applications are gonna be cloud native and the public cloud is just coming in like a big wave and people are gonna be driftwood or they'll be surfing the wave. Yeah, this is what's happening. >>Yeah, I think public cloud is an unstoppable megatrend. It's hit every other industry regulated industries like banking, right? Top secret industries like government. They all use the public cloud tells us the last, you know, standing old school industry and it's coming and I don't think we could have had an MWc without talking about open man. That's the other major shift. And so we're bringing both of those ideas here together in cloud city. So >>the big theme is telco transformation. Maybe we could start with the basics like paint a picture of what the telco infrastructure looks like, particularly the data center stuff because they all have big data centers >>because that's >>those are the candidates to go into the cloud explained to the audience. >>Well, do you have a time machine? I think if any of us were in tech in the late 90s and early 2000s, that's what telcos like today. Right. So for people outside of the industry don't know right there mostly still managing their own data centers, they're just sort of adopting virtualization. Some of the more advanced telcos are mostly virtualized public cloud. Is this idea that like this advanced thought and so yeah, I mean things are on premise, things are in silom, things don't use a P. I. S there all integrated with custom code. And so the transformation, we can all see it because we've lived it in other industries. And I'm bringing that to telco and say come along for the ride. It totally works and it's gonna be amazing. >>So it's hardened purpose built infrastructure. Okay. That ultimately parts of that need to go to the public cloud. Right. What parts do you see going first? >>I think all of it. Really. Yeah. And I think when you look at like dish in the W. S. Which was an announcement that came out about two months ago. Right. I mean dish was doing all these are FPs. Everyone knew about it. They were looking for a cloud native software and no one knew what they were. They knew a big part was open man. But their coupling open ran with AWS and deploying their parts of their network onto the public cloud and the whole industry is like wait we thought this was years away, right? Or number two, you're crazy. And I'm saying this is what I've been talking about guys. This is exactly what you can do, leverage the Capex over. Let's see. I think Amazon did $100 billion 2020 right, leverage that Capex for yourself. Get that infinite scalability right? It's going to, well we >>have, we have a saying here in the queue, we just made this up called D. R. That's your initial tucker. The digital revolution and the three Rs reset re platform and re factor. I think the observation we're seeing is that you're coming in with the narrative what everyone's kind of like they're waking up because they have to reset and then re platform with the cloud. But the opportunity is gonna be the re factoring, You're seeing the public cloud, do that already with the Enterprise Enterprises. Already re factoring has done that. Already done that now. Telcos the last area to be innovated by the cloud. >>Yeah, I think there's old school big, we're kind of on a hollowed ground here in the Ericsson booth that I took over, right? They bailed and I kind of made fun of them. I was like, they don't have anything to say, right, They're not going to go to the show. I'm like, this is this is a revolution that's happening in telco and I don't think the big guys are really interested in rewriting their software that frankly makes them billions and billions of dollars of revenue. And I'm like to use the public cloud. All of the software needs to be rewritten needs to be re factored and you've got to start training your teams on how to use it. They don't have any capability. The telcos, in terms of those skills hire the right people, retrain your teams, move your applications, rewrite them. And I think that's what we're talking, this is not a short journey, this is a 10 year journey. So >>let's fast forward to the future a little bit because when I look around cloud city, I see ecosystem everywhere. So as you well know, the telcos have generally done a poor job of attacking adjacent seas. So my question is can they go beyond should they go beyond connectivity or is that going to be the role of the ecosystem? >>Yeah, I think it's time that the telco starts to focus on their subscriber, right? It's been really easy for them to rely on the oligopoly of the network, Right? The network, we live in the United States, we see the 18 T Verizon T mobile five G network, five G network. Like what about us? Right. And it's really easy for the over the top players right, that come in and they're always, telcos are always complaining about being coming dumb pipes and I'm like, you don't focus on the customer, we would rather buy from an Apple and amazon if they provided a mobile service because the customer experience will be better. Right? They need to start focusing on us. They have great businesses but they want to make them better. They need to start focusing on the subscriber, so >>it's a partnership with the ecosystem then for them to go beyond just straight connectivity because you're right, those are the brands that we want to do business >>with. You know, there was a great survey, Peter Atherton who will be talking as a speaker I think um I can't remember when he's talking but he was talking about how there was a survey done, where would you rather get your mobile service from? And it had a couple of big names in telco and then of course the obvious, you know, consumer brands, the ones that we all know and it was like overwhelmingly would rather buy from an amazon or an apple. And I'm like, this is like if you guys don't change, right, if telco doesn't change they keep rolling out 60 and blah blah blah. It's about the network and I don't start making about the subscriber right? Those revenues are going to continue to erode and they just sit there and complain about the O. T. T. Players. Like it's time to fight back. Yeah, I own the subscriber >>relationship. It's a digital revolution and I think This event really encapsulates in my mind this hybrid world here because it's physical events back. It's been since 2019 winter that this event actually happened. >>Well no it was even longer than, well I guess winter it was February of 19, right? And so like you look at ericsson and some of the big names that dropped out of the show, the time they come back, three years will have passed three years, right? This is how you feel your sales funnel is how you connect with your customers right? Tokyo is a very global, you know experience and so you gotta, you gotta get in front of people and you got to talk a >>lot of change to its happened, look at just what public clouds done in 2.5 years. You imagine three years being just >>gone, right? And I think a lot of people back to edition A. W. S. I think the industry was a little bit surprised by that announcement. So I've been telling executives if you were surprised by that, if you think that's, you know, if you don't know how that's gonna work, you need to come to cloud cities, you start meeting all the vendors are here. We have over 30 vendors, 70 demos, right? People who are pushing the technology forward, you need to learn what's going on here. We have several dish vendors here. Come learn about open rand, come learn about public cloud. So >>we're tight on time today, but we're going to have you back and we want to get into the tech, Get it to open, ran a little bit, get into what 5G and beyond and how we're going to take advantage of that and monetize it and what that all means. >>And also we want to hear what's going on the hallways. I know you got a lot of your key noting, you're gonna be a lot of events, the yacht. You've got a lot of briefings, >>yep. Yeah, I've already had two meetings this morning. I shot a video. Um, I met with one of the world's largest groups and I met with a tiny little super app company. Right? So running the gamut, doing everything reporter >>now, we could be like our roaming >>reporter. You know, I love, I love talking to execs and telco getting their perspective on what is public cloud and where are they going, what are they thinking about? And you talked to people who really, really get it and you get people who are just nascent and everywhere in between and I love mwc it's going great. >>Daniel Rose and you are a digital revolution telco DDR. There's amazing. Davis has been fantastic. Again for the folks watching, this is a hybrid events, there's an online component and we're reaching out with our remote interviews to get people brought in and we're shipping this content out to the masses all over the world. It's gonna be really amazing cube coverages here. It's gonna be rocking you guys are doing great. I just want to give you a compliment that you guys just did an amazing job. And of course we've got adam in the studio with the team. So adam, I'm gonna pass it off back to you in the studio

>> Thank you, everyone for joining. I'm here today to talk about ingress controllers, API gateways, and service mesh on Kubernetes, three very hot topics that are also frequently confusing. So I'm Richard Li, founder/CEO of Ambassador Labs, formerly known as Datawire. We sponsor a number of popular open source projects that are part of the Cloud Native Computing Foundation, including Telepresence and Ambassador, which is a Kubernetes native API gateway. And most of what I'm going to talk about today is related to our work around Ambassador. So I want to start by talking about application architecture and workflow on Kubernetes and how applications that are being built on Kubernetes really differ from how they used to be built. So when you're building applications on Kubernetes, the traditional architecture is the very famous monolith. And the monolith is a central piece of software. It's one giant thing that you build deploy, run. And the value of a monolith is it's really simple. And if you think about the monolithic development process, more importantly is that architecture is really reflected in that workflow. So with a monolith, you have a very centralized development process. You tend not to release too frequently because you have all these different development teams that are working on different features, and then you decide in advance when you're going to release that particular piece of software and everyone works towards that release train. And you have specialized teams. You have a development team, which has all your developers. You have a QA team, you have a release team, you have an operations team. So that's your typical development organization and workflow with a monolithic application. As organizations shift to microservices, they adopt a very different development paradigm. It's a decentralized development paradigm where you have lots of different independent teams that are simultaneously working on different parts of this application, and those application components are really shipped as independent services. And so you really have a continuous release cycle because instead of synchronizing all your teams around one particular vehicle, you have so many different release vehicles that each team is able to ship as soon as they're ready. And so we call this full cycle development because that team is really responsible not just for the coding of that microservice, but also the testing and the release and operations of that service. So this is a huge change, particularly with workflow, and there's a lot of implications for this. So I have a diagram here that just tries to visualize a little bit more the difference in organization. With the monolith, you have everyone who works on this monolith. With microservices, you have the yellow folks work on the yellow microservice and the purple folks work on the purple microservice and maybe just one person work on the orange microservice and so forth. So there's a lot more diversity around your teams and your microservices, and it lets you really adjust the granularity of your development to your specific business needs. So how do users actually access your microservices? Well, with a monolith, it's pretty straightforward. You have one big thing, so you just tell the internet, well, I have this one big thing on the internet. Make sure you send all your traffic to the big thing. But when you have microservices and you have a bunch of different microservices, how do users actually access these microservices? So the solution is an API gateway. So the API gateway consolidates all access to your microservices. So requests come from the internet. They go to your API gateway. The API gateway looks at these requests, and based on the nature of these requests, it routes them to the appropriate microservice. And because the API gateway is centralizing access to all of the microservices, it also really helps you simplify authentication, observability, routing, all these different cross-cutting concerns, because instead of implementing authentication in each of your microservices, which would be a maintenance nightmare and a security nightmare, you've put all of your authentication in your API gateway. So if you look at this world of microservices, API gateways are a really important part of your infrastructure which are really necessary, and pre-microservices, pre-Kubernetes, an API gateway, while valuable, was much more optional. So that's one of the really big things around recognizing with the microservices architecture, you really need to start thinking much more about an API gateway. The other consideration with an API gateway is around your management workflow, because as I mentioned, each team is actually responsible for their own microservice, which also means each team needs to be able to independently manage the gateway. So Team A working on that microservice needs to be able to tell the API gateway, this is how I want you to route requests to my microservice, and the purple team needs to be able to say something different for how purple requests get routed to the purple microservice. So that's also a really important consideration as you think about API gateways and how it fits in your architecture, because it's not just about your architecture, it's also about your workflow. So let me talk about API gateways on Kubernetes. I'm going to start by talking about ingress. So ingress is the process of getting traffic from the internet to services inside the cluster. Kubernetes, from an architectural perspective, it actually has a requirement that all the different pods in a Kubernetes cluster needs to communicate with each other. And as a consequence, what Kubernetes does is it creates its own private network space for all these pods, and each pod gets its own IP address. So this makes things very, very simple for interpod communication. Kubernetes, on the other hand, does not say very much around how traffic should actually get into the cluster. So there's a lot of detail around how traffic actually, once it's in the cluster, how you route it around the cluster, and it's very opinionated about how this works, but getting traffic into the cluster, there's a lot of different options and there's multiple strategies. There's Pod IP, there's Ingress, there's LoadBalancer resources, there's NodePort. I'm not going to go into exhaustive detail on all these different options, and I'm going to just talk about the most common approach that most organizations take today. So the most common strategy for routing is coupling an external load balancer with an ingress controller. And so an external load balancer can be a hardware load balancer. It can be a virtual machine. It can be a cloud load balancer. But the key requirement for an external load balancer is to be able to attach a stable IP address so that you can actually map a domain name and DNS to that particular external load balancer, and that external load balancer usually, but not always, will then route traffic and pass that traffic straight through to your ingress controller. And then your ingress controller takes that traffic and then routes it internally inside Kubernetes to the various pods that are running your microservices. There are other approaches, but this is the most common approach. And the reason for this is that the alternative approaches really require each of your microservices to be exposed outside of the cluster, which causes a lot of challenges around management and deployment and maintenance that you generally want to avoid. So I've been talking about an ingress controller. What exactly is an ingress controller? So an ingress controller is an application that can process rules according to the Kubernetes ingress specification. Strangely, Kubernetes is not actually shipped with a built-in ingress controller. I say strangely because you think, well, getting traffic into a cluster is probably a pretty common requirement, and it is. It turns out that this is complex enough that there's no one size fits all ingress controller. And so there is a set of ingress rules that are part of the Kubernetes ingress specification that specify how traffic gets routed into the cluster, and then you need a proxy that can actually route this traffic to these different pods. And so an ingress controller really translates between the Kubernetes configuration and the proxy configuration, and common proxies for ingress controllers include HAProxy, Envoy Proxy, or NGINX. So let me talk a little bit more about these common proxies. So all these proxies, and there are many other proxies. I'm just highlighting what I consider to be probably the three most well-established proxies, HAProxy, NGINX, and Envoy Proxy. So HAProxy is managed by HAProxy Technologies. Started in 2001. The HAProxy organization actually creates an ingress controller. And before they created an ingress controller, there was an open source project called Voyager which built an ingress controller on HAProxy. NGINX, managed by NGINX, Inc., subsequently acquired by F5. Also open source. Started a little bit later, the proxy, in 2004. And there's the Nginx-ingress, which is a community project. That's the most popular. As well as the Nginx, Inc. kubernetes-ingress project, which is maintained by the company. This is a common source of confusion because sometimes people will think that they're using the NGINX ingress controller, and it's not clear if they're using this commercially supported version or this open source version. And they actually, although they have very similar names, they actually have different functionality. Finally, Envoy Proxy, the newest entrant to the proxy market, originally developed by engineers at Lyft, the ride sharing company. They subsequently donated it to the Cloud Native Computing Foundation. Envoy has become probably the most popular cloud native proxy. It's used by Ambassador, the API gateway. It's used in the Istio service mesh. It's used in the VMware Contour. It's been used by Amazon in App Mesh. It's probably the most common proxy in the cloud native world. So as I mentioned, there's a lot of different options for ingress controllers. The most common is the NGINX ingress controller, not the one maintained by NGINX, Inc., but the one that's part of the Kubernetes project. Ambassador is the most popular Envoy-based option. Another common option is the Istio Gateway, which is directly integrated with the Istio mesh, and that's actually part of Docker Enterprise. So with all these choices around ingress controller, how do you actually decide? Well, the reality is the ingress specification's very limited. And the reason for this is that getting traffic into a cluster, there's a lot of nuance into how you want to do that, and it turns out it's very challenging to create a generic one size fits all specification because of the vast diversity of implementations and choices that are available to end users. And so you don't see ingress specifying anything around resilience. So if you want to specify a timeout or rate-limiting, it's not possible. Ingress is really limited to support for HTTP. So if you're using gRPC or web sockets, you can't use the ingress specification. Different ways of routing, authentication. The list goes on and on. And so what happens is that different ingress controllers extend the core ingress specification to support these use cases in different ways. So NGINX ingress, they actually use a combination of config maps and the ingress resources plus custom annotations that extend the ingress to really let you configure a lot of the additional extensions that is exposed in the NGINX ingress. With Ambassador, we actually use custom resource definitions, different CRDs that extend Kubernetes itself to configure Ambassador. And one of the benefits of the CRD approach is that we can create a standard schema that's actually validated by Kubernetes. So when you do a kub control apply of an Ambassador CRD, kub control can immediately validate and tell you if you're actually applying a valid schema and format for your Ambassador configuration. And as I previously mentioned, Ambassador's built on Envoy Proxy, Istio Gateway also uses CRDs. They can be used in extension of the service mesh CRDs as opposed to dedicated gateway CRDs. And again, Istio Gateway is built on Envoy Proxy. So I've been talking a lot about ingress controllers, but the title of my talk was really about API gateways and ingress controllers and service mesh. So what's the difference between an ingress controller and an API gateway? So to recap, an ingress controller processes Kubernetes ingress routing rules. An API gateway is a central point for managing all your traffic to Kubernetes services. It typically has additional functionality such as authentication, observability, a developer portal, and so forth. So what you find is that not all API gateways are ingress controllers because some API gateways don't support Kubernetes at all. So you can't, they can't be ingress controllers. And not all ingress controllers support the functionality such as authentication, observability, developer portal, that you would typically associate with an API gateway. So generally speaking, API gateways that run on Kubernetes should be considered a superset of an ingress controller. But if the API gateway doesn't run on Kubernetes, then it's an API gateway and not an ingress controller. So what's the difference between a service mesh and an API gateway? So an API gateway is really focused on traffic into and out of a cluster. So the colloquial term for this is North/South traffic. A service mesh is focused on traffic between services in a cluster, East/West traffic. All service meshes need an API gateway. So Istio includes a basic ingress or API gateway called the Istio Gateway, because a service mesh needs traffic from the internet to be routed into the mesh before it can actually do anything. Envoy Proxy, as I mentioned, is the most common proxy for both mesh and gateways. Docker Enterprise provides an Envoy-based solution out of the box, Istio Gateway. The reason Docker does this is because, as I mentioned, Kubernetes doesn't come package with an ingress. It makes sense for Docker Enterprise to provide something that's easy to get going, no extra steps required, because with Docker enterprise, you can deploy it and get going, get it exposed on the internet without any additional software. Docker Enterprise can also be easily upgraded to Ambassador because they're both built on Envoy. It ensures consistent routing semantics. And also with Ambassador, you get greater security for single sign-on. There's a lot of security by default that's configured directly into Ambassador. Better control over TLS, things like that. And then finally, there's commercial support that's actually available for Ambassador. Istio is an open source project that has a very broad community, but no commercial support options. So to recap, ingress controllers and API gateways are critical pieces of your cloud native stack. So make sure that you choose something that works well for you. And I think a lot of times organizations don't think critically enough about the API gateway until they're much further down the Kubernetes journey. Considerations around how to choose that API gateway include functionality such as how does it do with traffic management and observability? Does it support the protocols that you need? Also nonfunctional requirements such as does it integrate with your workflow? Do you offer commercial support? Can you get commercial support for this? An API gateway is focused on North/South traffic, so traffic into and out of your Kubernetes cluster. A service mesh is focused on East/West traffic, so traffic between different services inside the same cluster. Docker Enterprise includes Istio Gateway out of the box. Easy to use, but can also be extended with Ambassador for enhanced functionality and security. So thank you for your time. Hope this was helpful in understanding the difference between API gateways, ingress controllers, and service meshes, and how you should be thinking about that on your Kubernetes deployment.

(upbeat music) >> From our studios, in the heart of Silicon Valley, Palo Alto, California, this is a CUBE Conversation. >> Okay, welcome back everyone. We're here in Palo Alto, California at the CUBE studios. I'm John Furrier, host of theCUBE. For a special CUBE conversation, a preview of the upcoming KubeCon, Cloud Native Con in San Diego. Where theCUBE will be there, as well as a bunch of other folks. The New Stack will be there, a lot of other media producers, as well as the big conference. KubeCon, in it's fourth or fifth year, depending on which year you count. Its a super exciting conference, this is where the Kubernetes and the Cloud Native communities come together to set the agenda to talk about all the great things that are going on in the industry and how it's changing tech for good. We're here with Vicki Cheung, who is the Co-Chair and also Software Engineer Manager at Lyft. Vicki great to see you, thanks for coming in. >> Thanks for having me. >> I'm so proud of KubeCon and the community because when we were there, in the early days, when it was kind of forming and created. There was a big vision that it would play a critical role. A lot of people haven't really seen how big it's become. And it's really become so important that the big companies are now moving towards Open Source, the CNC has been very successful. Both on getting vendors in and end user projects. You're setting the agenda. You're setting the table for this year's KubeCon. >> Yeah. >> Tell us what's going on. >> Yeah, I think we're seeing the maturity of the community coming together. It's sort of continuing on this trend where, as you said, the adoption is growing exponentially. I think, that two years ago if you surveyed the room and asked people, "who is using Kubernetes and Docker in production, you'd maybe get, like, a hand. I think you're seeing this thing where, this trend, where this year, I think, if you surveyed the room, it would be like maybe half the room were raising their hands. >> And the acceleration is interesting. You're seeing in, I mean, huge acceleration of the adoption of Kubernetes and other projects. And I think what's interesting to me, and I think commentary that we've been reporting on is that Kubernetes can be that unifying point. And you're seeing this, de facto standard emerging and a lot of people talking about that de facto. And that has accelerated the Production Use Cases. So, the End User Projects are increasing. Is that going to be a focus or main focus of this year's KubeCon? >> Oh yeah, definitely. I think we're seeing, maybe even last year, we've had a lot of end user talks from, you know, early adopters start ups, like tech giants. But this year we're seeing a lot more enterprise use cases. And that's driving a lot of content as well. So, I think when it comes enterprise use cases, we're seeing a lot of talks around security and governance. We're seeing a lot of developer productivity talks, and we're also seeing a lot more focus on how to scale operations. >> So, take me through the focus this year. Let's get this out on the table, because this is a big event. What can people expect this year, when you guys sat in the room, with the teams, and said, "Okay, here's going to be the Con and agenda, "we have a form of that's not broken, let's not fix, what's not broken, so the format's good." What was the focus, what was this year's focus. What's going to be the focus of this year's KubeCon? >> Yeah, I think Bryan and I, when we sit together, we have all the tracks that we've been using, for the last couple of years. And generally we, sort of stick to them, because they're pretty good. But the way we, I think the interesting thing is, we see over the years how the distribution across the tracks have changed. So, for example, I think this year, operations is a super big track, and it's very competitive to get into. And that's because we're seeing a lot more adoption at scale, and different Use cases, different types of companies and production. So, I think that track have been a main focus. And also, I think customizing Kubernetes is another one, as people's use cases got more sophisticated. And in the serve use case track, I think we see a lot more enterprise, like even banks adopting Kubernetes. >> So, essentially the same game as before, but weighting them differently based on adoption? >> Exactly, I think it's a shift, like earlier it would be maybe more like earlier adopter and serve experimental use cases, and now it's like, people are actually going into production now. So, the shift has been into like, how do we get this running reliably, at scale. So, that's what we're seeing. >> In terms of the industry, if you look back, and again you guys went public at Lyft, and you guys are growing, and you guys have a great open source product with Envoy, I'm sure you guys are going to do the Day Zero thing again this year, last year was a big success. Is there any projects that you see coming out of the woodwork that are going to evolve up? And what can people expect in terms of project growth or emerging projects. Is there any indication, from your standpoint? What's going to come out of the community? >> Yeah, I think there's a lot of projects that are growing, like Helm continues to grow. I think one thing that I'm seeing, from this year's content is there's a lot of focus on, OPA. Like I said, the security is sort of a growing focus. And OPA is certainly one of the things I think people should expect at this year's conference. Another area that I'm personally very interested in, and I see, I'm happy to see it popping up more this year, is developer experience and developer productivity. As we're, even just personally witnessing at Lyft, adopting Cloud Native Architecture, microservices and Kubernetes, comes with a lot of benefits, but also a lot of new challenges into how people should develop in this ecosystem. So, there are projects like Telepresence and Tilt that are coming up more. And there's a few talks around that, in application and development as well. >> How about the developer's side? What's the general sentiment in the community these days? If you had to kind of, put a parameter out there, what's the general vibe in the community, from a developer's stand point around Cloud Native and Kubernetes? >> I think there's, I think it depends on who you ask. Generally, you know, people are very very excited to be sort of moving in this direction. And I think it allows people to be a lot more flexible in how they develop their applications. But I also think that there's a lot of open questions, that we still have to answer. And this is where, I guess some of these new projects come into help fill the gap. >> Well first of all, you guys have, always have a great conference, theCUBE will be there, as well media producer will be a lot on digital. So, folks not going to the event, they should go and see the face-to-face. I want to get the take on some of the submissions. You guys have an interesting dynamic and CNCF and KubeCon and Cloud Native Con, you have a ton of end user projects, A lot of end user focus, obviously it's an end user focused show. But you also have a lot of vendors, suppliers that are also in the community. So, you have an interesting balance going on. Talk about some of the numbers in terms of submissions, because I know, everyone's got submissions, not everyone gets accepted, like the operations you mentioned is a hot track. What's some of the numbers? Can you share any, kind of statistics around number of submissions versus acceptance? >> Yeah, I think typically CNCF will publish some of the numbers, in a blog post. So, I don't know all the numbers off the top of my head. But for example, in operations, I think the acceptance rate was maybe less than 10%. I think, it wasn't that competitive, maybe two years ago, but certainly as everyone moves to deploying Kubernetes on their own, that's sort of a hot topic. >> What's the relationship in the community, with the big vendors? Obviously you see, Amazon, Google, Microsoft, are big players in there, and they're investing heavily in Kubernetes. And VMware, as well, is also investing. Is that good, bad, is it just balancing? What's the communities view on the participation of the big guys? >> Yeah, I think it's actually been really great to the community and I personally would not have expected Microsoft, ADBS to be as active in the community as they are now, if you asked me five years ago. So, I think it's this interesting thing that Kubernetes and CNCF hasn't managed to do, is instead of having the tech giants having to suck out the energy and the technology into their private ecosystem. It's been the other way around. Where Microsoft and ADBS and Google have been contributing a lot of their integrations and other tooling and projects that they've built on top of the projects in CNCF. And just enriching the community. >> So, you're saying that they've been pushing more towards open source, not pulling out of it? >> Yeah. I think that's, obviously I'm super happy to see that. But I think that was not obvious at all from the beginning. >> Yeah, it's super exciting, you know we've been tracking the business model's evolution. And open source is more powerful than ever before now. And it's growing so fast and changing. Let's talk about the Enterprises now, because I think you're seeing adoption on the classic IT Enterprise moving in. We've interviewed many CSO's, CIO's and practitioners, they all have the same kind of reaction, "Oh my God, this is so good for our business, "Kubernetes what Containers are doing, "will allow us to manage the life cycle of our applications. "The same time bringing Cloud Native, "without a lot of disruption." What's your reaction to that, are you guys seeing that same dynamic? And if so, what is some of the use cases of Enterprises, within KubeCon? >> Yeah, I think one thing is, the earlier pitch is the, of course allows you to have that flexibility to move from your data center to Hybrid Cloud, and maybe to different cloud vendors. So, I think that's super appealing. But another thing that we're seeing this year is, as people adopted at scale they're also seeing a lot of cost savings from adopting Kubernetes, just because it allows them to be a lot more flexible in how they deploy things. I think that, in general as you move to serve a community standard, an Open Source Platform, it does help your developers a lot, because now they don't need to build their own in-house thing, which is, for example, what Lyft had before Kubernetes. So, I think it's generally a productivity win. >> So, on Envoy real quick, while I got you here. Lyft has been involved in donating that project and driving it last year, one of the most notable news, at least from out observation was, that the Envoy did that event the day before. And it was really popular. >> Yeah >> Is it going to happen again? What's some of the views on that? >> Yeah, so EnvoyCon is happening again this year, right before Kubernetes. I think it's even more popular than last year. So, there's going to be a lot of talks around, running Envoy at scale, and also on top of Kubernetes. As people sort of integrate the two technologies more. >> Okay, so I got to ask you the personal observations, you can take your Co-Chair hat off and put your KubeCon community hat on. What dark horses are out there, that you think may surprise people this year? What do you think might happen? Because there is always something that goes on, that's just a surprise, a dark horse, if you will, comes out of the woodwork, what do you think might happen? >> Well, I think there's of course going to be a few new Open Source projects that are launched there. And I also think there will be a lot of, maybe more than usual, interesting people that people can meet at the conference. >> I heard there's a rumor that the original gangsters, or the OG's or the original members, the seven original members are going to be there. >> Yeah, I don't-- >> Confirm or deny? >> I don't know if I can confirm or deny, but-- >> Okay, I think that's a yes, possibly. We'll be tracking that, okay, final question for you. What do you think will be the most important story for people to pay attention to this year? What do you think is going to be, evolving out on the stage? Out on the tracks, out on digital? What do you expect to see this year? What is some of the top stories and top notable points that you think is going to happen this year? >> Yeah, I think one thing that maybe, for me, and for a lot of people is this message that Kubernetes is ready. I think it's been sort of building up in this hype for the last few years. And we've seen adoption, but I think this is truly the year that I see a lot of Enterprise end user cases and I can really say that Kubernetes is ready. >> So the new criteria is proof points? Scale, operationally seeing some operations, real proof points, customer adoption, enterprise and hyperscalers? >> Yeah. >> All right, Vicki thanks for coming in and sharing this preview on KubeCon, Cloud Native Con. It's theCUBE covering the KubeCon, Cloud Native Con preview with Vicki Co-Chair, who set the agenda with her fellow Co-Chair Bryan Liles, as well. Great to have her on and share upcoming conversation around KubeCon. I'm John Furrier, thanks for watching. (upbeat music)

>> From Cambridge, Massachusetts, it's theCUBE. Covering MIT Chief Data Officer and Information Quality Symposium 2019. Brought to you by SiliconANGLE Media. (futuristic music) >> Welcome back to Cambridge, Massachusetts everybody. You're watching theCUBE, the leader in live tech coverage. We go out to the events and we extract the signal from the noise. This is day two, we're sort of wrapping up the Chief Data Officer event. It's MIT CDOIQ, it started as an information quality event and with the ascendancy of big data the CDO emerged and really took center stage here. And it's interesting to know that it's kind of come full circle back to information quality. People are realizing all this data we have, you know the old saying, garbage in, garbage out. So the information quality worlds and this chief data officer world have really come colliding together. Robert Abate is here, he's the Vice President and CDO of Global IDS and also the co-chair of next year's, the 14th annual MIT CDOIQ. Robert, thanks for coming on. >> Oh, well thank you. >> Now you're a CDO by background, give us a little history of your career. >> Sure, sure. Well I started out with an Electrical Engineering degree and went into applications development. By 2000, I was leading the Ralph Lauren's IT, and I realized when Ralph Lauren hired me, he was getting ready to go public. And his problem was he had hired eight different accounting firms to do eight different divisions. And each of those eight divisions were reporting a number, but the big number didn't add up, so he couldn't go public. So he searched the industry to find somebody who could figure out the problem. Now I was, at the time, working in applications and had built this system called Service Oriented Architectures, a way of integrating applications. And I said, "Well I don't know if I could solve the problem, "but I'll give it a shot." And what I did was, just by taking each silo as it's own problem, which was what EID Accounting Firm had done, I was able to figure out that one of Ralph Lauren's policies was if you buy a garment, you can return it anytime, anywhere, forever, however long you own it. And he didn't think about that, but what that meant is somebody could go to a Bloomingdale's, buy a garment and then go to his outlet store and return it. Well, the cross channels were different systems. So the outlet stores were his own business, retail was a different business, there was a completely different, each one had their own AS/400, their own data. So what I quickly learned was, the problem wasn't the systems, the problem was the data. And it took me about two months to figure it out and he offered me a job, he said well, I was a consultant at the time, he says, "I'm offering you a job, you're going to run my IT." >> Great user experience but hard to count. >> (laughs) Hard to count. So that's when I, probably 1999 was when that happened. I went into data and started researching-- >> Sorry, so how long did it take you to figure that out? You said a couple of months? >> A couple of months, I think it was about two months. >> 'Cause jeez, it took Oracle what, 10 years to build Fusion with SOA? That's pretty good. (laughs) >> This was a little bit of luck. When we started integrating the applications we learned that the messages that we were sending back and forth didn't match, and we said, "Well that's impossible, it can't not match." But what didn't match was it was coming from one channel and being returned in another channel, and the returns showed here didn't balance with the returns on this side. So it was a data problem. >> So a forensics showdown. So what did you do after? >> After that I went into ICICI Bank which was a large bank in India who was trying to integrate their systems, and again, this was a data problem. But they heard me giving a talk at a conference on how SOA had solved the data challenge, and they said, "We're a bank with a wholesale, a retail, "and other divisions, "and we can't integrate the systems, can you?" I said, "Well yeah, I'd build a website "and make them web services and now what'll happen is "each of those'll kind of communicate." And I was at ICICI Bank for about six months in Mumbai, and finished that which was a success, came back and started consulting because now a lot of companies were really interested in this concept of Service Oriented Architectures. Back then when we first published on it, myself, Peter Aiken, and a gentleman named Joseph Burke published on it in 1996. The publisher didn't accept the book, it was a really interesting thing. We wrote the book called, "Services Based Architectures: A Way to Integrate Systems." And the way Wiley & Sons, or most publishers work is, they'll have three industry experts read your book and if they don't think what you're saying has any value, they, forget about it. So one guy said this is brilliant, one guy says, "These guys don't know what they're talking about," and the third guy says, "I don't even think what they're talking about is feasible." So they decided not to publish. Four years later it came back and said, "We want to publish the book," and Peter said, "You know what, they lost their chance." We were ahead of them by four years, they didn't understand the technology. So that was kind of cool. So from there I went into consulting, eventually took a position as the Head of Enterprise and Director of Enterprise Information Architecture with Walmart. And Walmart, as you know, is a huge entity, almost the size of the federal government. So to build an architecture that integrates Walmart would've been a challenge, a behemoth challenge, and I took it on with a phenomenal team. >> And when was this, like what timeframe? >> This was 2010, and by the end of 2010 we had presented an architecture to the CIO and the rest of the organization, and they came back to me about a week later and said, "Look, everybody agrees what you did was brilliant, "but nobody knows how to implement it. "So we're taking you away, "you're no longer Director of Information Architecture, "you're now Director of Enterprise Information Management. "Build it. "Prove that what you say you could do, you could do." So we built something called the Data CAFE, and CAFE was an acronym, it stood for: Collaborative Analytics Facility for the Enterprise. What we did was we took data from one of the divisions, because you didn't want to take on the whole beast, boil the ocean. We picked Sam's Club and we worked with their CFO, and because we had information about customers we were able to build a room with seven 80 inch monitors that surrounded anyone in the room. And in the center was the Cisco telecommunications so you could be a part of a meeting. >> The TelePresence. >> TelePresence. And we built one room in one facility, and one room in another facility, and we labeled the monitors, one red, one blue, one green, and we said, "There's got to be a way where we can build "data science so it's interactive, so somebody, "an executive could walk into the room, "touch the screen, and drill into features. "And in another room "the features would be changing simultaneously." And that's what we built. The room was brought up on Black Friday of 2013, and we were able to see the trends of sales on the East Coast that we quickly, the executives in the room, and these are the CEO of Walmart and the heads of Sam's Club and the like, they were able to change the distribution in the Mountain Time Zone and west time zones because of the sales on the East Coast gave them the idea, well these things are going to sell, and these things aren't. And they saw a tremendous increase in productivity. We received the 2014, my team received the 2014 Walmart Innovation Project of the Year. >> And that's no slouch. Walmart has always been heavily data-oriented. I don't know if it's urban legend or not, but the famous story in the '80s of the beer and the diapers, right? Walmart would position beer next to diapers, why would they do that? Well the father goes in to buy the diapers for the baby, picks up a six pack while he's on the way, so they just move those proximate to each other. (laughs) >> In terms of data, Walmart really learned that there's an advantage to understanding how to place items in places that, a path that you might take in a store, and knowing that path, they actually have a term for it, I believe it's called, I'm sorry, I forgot the name but it's-- >> Selling more stuff. (laughs) >> Yeah, it's selling more stuff. It's the way you position items on a shelf. And Walmart had the brilliance, or at least I thought it was brilliant, that they would make their vendors the data champion. So the vendor, let's say Procter & Gamble's a vendor, and they sell this one product the most. They would then be the champion for that aisle. Oh, it's called planogramming. So the planogramming, the way the shelves were organized, would be set up by Procter & Gamble for that entire area, working with all their other vendors. And so Walmart would give the data to them and say, "You do it." And what I was purporting was, well, we shouldn't just be giving the data away, we should be using that data. And that was the advent of that. From there I moved to Kimberly-Clark, I became Global Director of Enterprise Data Management and Analytics. Their challenge was they had different teams, there were four different instances of SAP around the globe. One for Latin America, one for North America called the Enterprise Edition, one for EMEA, Europe, Middle East, and Africa, and one for Asia-Pacific. Well when you have four different instances of SAP, that means your master data doesn't exist because the same thing that happens in this facility is different here. And every company faces this challenge. If they implement more than one of a system the specialty fields get used by different companies in different ways. >> The gold standard, the gold version. >> The golden version. So I built a team by bringing together all the different international teams, and created one team that was able to integrate best practices and standards around data governance, data quality. Built BI teams for each of the regions, and then a data science and advanced analytics team. >> Wow, so okay, so that makes you uniquely qualified to coach here at the conference. >> Oh, I don't know about that. (laughs) There are some real, there are some geniuses here. >> No but, I say that because these are your peeps. >> Yes, they are, they are. >> And so, you're a practitioner, this conference is all about practitioners talking to practitioners, it's content-heavy, There's not a lot of fluff. Lunches aren't sponsored, there's no lanyard sponsor and it's not like, you know, there's very subtle sponsor desks, you have to have sponsors 'cause otherwise the conference's not enabled, and you've got costs associated with it. But it's a very intimate event and I think you guys want to keep it that way. >> And I really believe you're dead-on. When you go to most industry conferences, the industry conferences, the sponsors, you know, change the format or are heavily into the format. Here you have industry thought leaders from all over the globe. CDOs of major Fortune 500 companies who are working with their peers and exchanging ideas. I've had conversations with a number of CDOs and the thought leadership at this conference, I've never seen this type of thought leadership in any conference. >> Yeah, I mean the percentage of presentations by practitioners, even when there's a vendor name, they have a practitioner, you know, internal practitioner presenting so it's 99.9% which is why people attend. We're moving venues next year, I understand. Just did a little tour of the new venue, so, going to be able to accommodate more attendees, so that's great. >> Yeah it is. >> So what are your objectives in thinking ahead a year from now? >> Well, you know, I'm taking over from my current peer, Dr. Arka Mukherjee, who just did a phenomenal job of finding speakers. People who are in the industry, who are presenting challenges, and allowing others to interact. So I hope could do a similar thing which is, find with my peers people who have real world challenges, bring them to the forum so they can be debated. On top of that, there are some amazing, you know, technology change is just so fast. One of the areas like big data I remember only five years ago the chart of big data vendors maybe had 50 people on it, now you would need the table to put all the vendors. >> Who's not a data vendor, you know? >> Who's not a data vendor? (laughs) So I would think the best thing we could do is, is find, just get all the CDOs and CDO-types into a room, and let us debate and talk about these points and issues. I've seen just some tremendous interactions, great questions, people giving advice to others. I've learned a lot here. >> And how about long term, where do you see this going? How many CDOs are there in the world, do you know? Is that a number that's known? >> That's a really interesting point because, you know, only five years ago there weren't that many CDOs to be called. And then Gartner four years ago or so put out an article saying, "Every company really should have a CDO." Not just for the purpose of advancing your data, and to Doug Laney's point that data is being monetized, there's a need to have someone responsible for information 'cause we're in the Information Age. And a CIO really is focused on infrastructure, making sure I've got my PCs, making sure I've got a LAN, I've got websites. The focus on data has really, because of the Information Age, has turned data into an asset. So organizations realize, if you utilize that asset, let me reverse this, if you don't use data as an asset, you will be out of business. I heard a quote, I don't know if it's true, "Only 10 years ago, 250 of the Fortune 10 no longer exists." >> Yeah, something like that, the turnover's amazing. >> Many of those companies were companies that decided not to make the change to be data-enabled, to make data decision processing. Companies still use data warehouses, they're always going to use them, and a warehouse is a rear-view mirror, it tells you what happened last week, last month, last year. But today's businesses work forward-looking. And just like driving a car, it'd be really hard to drive your car through a rear-view mirror. So what companies are doing today are saying, "Okay, let's start looking at this as forward-looking, "a prescriptive and predictive analytics, "rather than just what happened in the past." I'll give you an example. In a major company that is a supplier of consumer products, they were leading in the industry and their sales started to drop, and they didn't know why. Well, with a data science team, we were able to determine by pulling in data from the CDC, now these are sources that only 20 years ago nobody ever used to bring in data in the enterprise, now 60% of your data is external. So we brought in data from the CDC, we brought in data on maternal births from the national government, we brought in data from the Census Bureau, we brought in data from sources of advertising and targeted marketing towards mothers. Pulled all that data together and said, "Why are diaper sales down?" Well they were targeting the large regions of the country and putting ads in TV stations in New York and California, big population centers. Birth rates in population centers have declined. Birth rates in certain other regions, like the south, and the Bible Belt, if I can call it that, have increased. So by changing the marketing, their product sales went up. >> Advertising to Texas. >> Well, you know, and that brings to one of the points, I heard a lecture today about ethics. We made it a point at Walmart that if you ran a query that reduced a result to less than five people, we wouldn't allow you to see the result. Because, think about it, I could say, "What is my neighbor buying? "What are you buying?" So there's an ethical component to this as well. But that, you know, data is not political. Data is not chauvinistic. It doesn't discriminate, it just gives you facts. It's the interpretation of that that is hard CDOs, because we have to say to someone, "Look, this is the fact, and your 25 years "of experience in the business, "granted, is tremendous and it's needed, "but the facts are saying this, "and that would mean that the business "would have to change its direction." And it's hard for people to do, so it requires that. >> So whether it's called the chief data officer, whatever the data czar rubric is, the head of analytics, there's obviously the data quality component there whatever that is, this is the conference for, as I called them, your peeps, for that role in the organization. People often ask, "Will that role be around?" I think it's clear, it's solidifying. Yes, you see the chief digital officer emerging and there's a lot of tailwinds there, but the information quality component, the data architecture component, it's here to stay. And this is the premiere conference, the premiere event, that I know of anyway. There are a couple of others, perhaps, but it's great to see all the success. When I first came here in 2013 there were probably about 130 folks here. Today, I think there were 500 people registered almost. Next year, I think 600 is kind of the target, and I think it's very reasonable with the new space. So congratulations on all the success, and thank you for stepping up to the co-chair role, I really appreciate it. >> Well, let me tell you I thank you guys. You provide a voice at these IT conferences that we really need, and that is the ability to get the message out. That people do think and care, the industry is not thoughtless and heartless. With all the data breaches and everything going on there's a lot of fear, fear, loathing, and anticipation. But having your voice, kind of like ESPN and a sports show, gives the technology community, which is getting larger and larger by the day, a voice and we need that so, thank you. >> Well thank you, Robert. We appreciate that, it was great to have you on. Appreciate the time. >> Great to be here, thank you. >> All right, and thank you for watching. We'll be right back with out next guest as we wrap up day two of MIT CDOIQ. You're watching theCUBE. (futuristic music)

>> Narrator: Live from San Francisco, it's theCUBE. Covering DevNet Create 2017. Brought to you by Cisco. (upbeat techno music) >> Hello everyone, welcome back to our live coverage here in San Francisco for Cisco Systems' inaugural DevNet Create event. I'm John Furrier sitting with my co-host Peter Burris, Head of Research at Wikibon.com. Our next guest is Jose Bogarin, Chief Innovation Officer, Altus Consulting, VIP here at Cisco DevNet Create. Welcome to theCUBE. >> Thank you. >> So tell your story, you have a really special story of true transformation, where DevNet and being a developer in this new world order has changed things for you. >> Yeah, actually people from Cisco call it a rags to riches story. Basically I founded my company 10 years ago with my brother and a friend. And business was going good, but we were having some trouble competing with the larger Cisco partners in Costa Rica. So that's why we decided to do something else and software was the way to go. So three years ago I had the opportunity participate in the first DevNet Zone in Cisco Live in San Francisco in 2014. And that really was a turning point for my company because we actually shifted our focus to the software and software development and that really pushed us forward and really allowed us to compete with those big partners, but also expand our business to some other parts of Latin America. So now we're doing stuff also in Mexico, and doing stuff in Peru, and even thinking about coming to the States and doing some software developing here. >> You're like, taking over the world. So take us through specifically the inflection point. Obviously DevNet, you had an internal compass, you felt that, kind of the tailwind of the marketplace pretty, not obvious to everyone, but you guys saw it. What was the moment where you go wow, we're on to something with this? >> Yeah, it's probably hard to say because it's less, like, different moments. The first one I think is reading Andreessen Horowitz, >> Peter: Andreessen Horowitz? >> Yeah, exactly. >> Peter: The Venture capitalist. >> Yeah reading their blog post about softwares in the world. So that was a blog post in 2011 I think. But we read about it in maybe 2013. And we started thinking, hey, maybe the way to go is actually to do some software by ourselves and figure out if we can actually improve the Cisco solutions that we are selling right now using software. So, we basically used that and then we came to the San Francisco 2014 DevNet Zone and said, hey, now Cisco has a program around this, so maybe yeah, software is the way to go. Maybe software is the way to actually go ahead and innovate, and do some other stuff to better serve our customers. So that's when we actually went back home and doubled down around on our strategy. And started developing more software, and having more conversations with our clients that we were able to solve using Cisco technology and Cisco hardware, but also develop software around it. >> Why did customers resonate with your story? Was it because you had a unique differentiator? What specifically did you do with Cisco that made it such a high impact value proposition? >> Okay, one of the things that I really like about Cisco is they have a very robust infrastructure, but it's sometimes, or you need special integrations to really solve a business need for a customer. So a lot of customers that we had, really had maybe the hardware or the platform, for example the Cisco Contact Center, but there's a gap between having the infrastructure and really solving that business need. So when we got there and told them, hey, maybe we can have those skills, or we are building those skills in our company to bridge that gap, that really made the difference with our customers. And that's our whole business in past three or four years has really been about that basically. >> And so it gave you an opportunity to get into that market and just have good products, great! What was the biggest learnings that you've had over that journey? What's the learnings you could share with folks watching? >> Okay, the first of all that it's a complete shift in your company. If you've been selling hardware, and now developing software. It's two different worlds completely. I don't want to say it's easier to sell hardware, but it's maybe more complicated to develop software. It has to be a whole different process because when you are selling hardware, you're basically doing the design and then just buying the hardware from Cisco and then selling it to your customer. But when you're developing software you have to have your team ready, develop probably three, four, five months, or even six months in advance. And then get that solution to the customer. So it takes a while and you have to change all your business, you have to change your practice. It's difficult. I know that a lot of partners are trying to move in that way and develop more software, but to be honest it's not that easy. You have to have a lot of commitment from management to actually make it. >> But I presume you're developing software not just for the hardware in terms of management, or something like that. Are you also looking at WebEx, and TelePresence, and the full suite of Cisco products as you start thinking about how you're developing solutions for your customers? Is that kind of the direction you're taking? Obviously on top of the hardware. Is that kind of the direction you're taking? >> Yeah, we actually started more around Contact Center and then mainly around collaboration so, WebEx presence and now even Cisco Spark. That was our focus for the first maybe three years and now we're starting to do stuff around networking, like traditional networking like routers, switching, or stuff like AP Key M or CMX for the wireless part, or even Meraki gear. So we started in collaboration but now we're expanding our business to other parts within the Cisco portfolio. >> As you think about this message of how the network, which has now become programmable, so in other words you can use software to define and reconfigure, rapidly reconfigure the network, are you also then seeing yourselves working not just with the traditional network people within the companies you're selling to, but also developers in showing how the network is offering a more superior, or extending the quality of the target that they're writing to as they write software? >> Yeah, and it's quite interesting. And coming from that Contact Center side, our conversations moved from IT to the supervisors and teams supervising the Contact Center, and now going to networking we'll probably have to move the conversations from the operations team now to the development team. So when you start developing software you actually have to go to the line of business, or to teams different from that operational team that you used to talk to. >> I was going to say, that's probably one of the reasons why it becomes more complex. That the change management challenges, and a partner has to fit into those for installing a new switch, or installing a new router is one thing. But the change management practices of going in and evolving the way a Contact Center operates, and I know Costa Rica is one of the places where, at least here in the US, it serves Spanish speaking communities here in the US. That's a pretty significant challenge. There's a lot of change management things that have to happen there. To be dragged into those is not a trivial exercise, but it also points up the need for more intelligent, higher-rope, more easy to manage, more robust types of networking interfaces. Where do you see the network going as a resource for developers to hit? >> I can say that it has to become easier to program the network because right now you have a lot of technologies, but they're still not there yet. You still need a lot of network background to actually use them, and some of them are not very flexible. So those technologies need to evolve for the developers to actually use them. And I see that coming in the next few years and Cisco's made a lot of progress in that. And also what we're seeing it's that need to improve the analytics and information that you can get from the network. And again Cisco, for example, has made a lot of progress in that. >> John: Well, AppDynamics. >> Exactly. With things like AppDynamics, or for example, APIs like Data in Motion, or the whole thought computing process that they have and that needs to improve for the developers to actually start getting more use out of it. >> What's next for you now that you see DevNet Create? They're puttin' their toe in the water, doing a good job here. First inaugural event. Does this have legs, this event? Yeah, yeah, I've seen it. I wasn't there during first DevNet Zone in 2014 and I've seen the growth from 2014 to 2015 in San Diego, and then Vegas, and then Vegas this year. So I've seen that grow in the DevNet Zone. I'm completely confident that the DevNet Create is going to get bigger and bigger in the coming years because I've seen how other teams, networking teams, operational teams, like people from Data Center, traditional like computer teams, they're starting to get more interested in software development and events like this. >> So based on your first signals of the first year of DevNet, which you walked in and transformed your business, you feel a similar vibe here? >> Oh yeah, yeah, totally, yeah, completely. You get that vibe of people learning, people start to say hey, Cisco's really actually sponsoring this and is actually putting their money where their mouth is. They're actually investing-- >> And the content's good. That's to me, the tell is the content. >> Peter: It's called walkin' the walk. >> Yeah, exactly, they're really, really helping the developers and you can see that. >> Well, let's hope that it translates to the core of Cisco because it's a huge company. The network engineers in the past, their diversion of developer was using Voice-over-IP. Those worlds are over, not over, but they're subsumed by cloud, right. Cloud is changing everything. So what are you most excited about right now as an entrepreneur, recovered, you're back on your way, rags to riches, talk of the town. As you look out on the horizon, the 20 mile stare. What are you excited about that are enabling you to go out and do what you're doing, what technologies? >> Yeah, well probably I know that some of them it's like buzz words, like IoT and cloud and machine learning and even blockchain. But actually having those technologies at hand, and it's not like you have to choose every one of them but actually use them, some of them, to actually build a better product or better service to your customers. It's something that really excites me. And again, it's something that Cisco's really investing in. So getting that traditional Cisco mold, it's like networking or Contact Center and actually improve those technologies with machine learning or some IoT technology, I think that's the way forward. And we're actually doubling down our investment in those technologies. >> Jose, thanks so much for coming on CUBE, sharing your story, I really appreciate it. Congratulations. >> Thank you, thank you so much. >> Peter: And you've got to get us down to Costa Rica. >> Sure, anytime. >> We've got to get down there. Half of Palo Alto goes down there, so we might as well Peter. (laughing) Seriously, thanks for coming on, great to have you. It's theCUBE live coverage in San Francisco for Cisco's inaugural event, DevNet Create. Building on the popular, only three year old DevNet program. I'm John Furrier, with Peter Burris with theCUBE. Stay tuned for more live coverage. Stay with us after this short break. (upbeat techno music) >> Hi I'm April Mitchell and I'm the Senior Director of Strategy and Plan.