 It's theCUBE, covering Sapphire Now 2017. Brought to you by SAP Cloud Platform and HANA Enterprise Cloud. Okay, welcome back everyone to our special Sapphire Now 2017 coverage. From our studio, I want to thank SAP Cloud Platform and SAP Enterprise Cloud for sponsoring our three day coverage, allow us to go out and do some regional content. Also, we have Google IO going on, some coverage there, we'll get some of those segments on. Also, other events going all around tech. Wanted to bring in to this studio session for discussion is Bill Norton, a CUBE alumni. The chief scientist at Console Connect, also known as Dr. Peering, a real expert in on networking and how networks are built and how they run and the impact of how packets move around the network. And of course, networks are being abstracted away to software and of course, no better person to talk about software defined networking, the changes in the network landscape and more importantly, the security implications. Bill Norton here inside our CUBE conversation. Good to see you again. Great to see you, John. So you got a couple of white papers. I wanted to call you in two, under two-fold. One, a lot of SIFT going on the network, okay. As much as people are moving up the stack as fast as they can, the network still has got a lot of action going on. Software defined, scaling issues, now security issues. Still an important part, you still got to move the packet from point A to point B. Now things, the cloud has certainly escalated the conversation. Absolutely. Your thoughts? We're at a crossroads right now. We have two forces that are colliding. The first is increased dependence on the cloud as more companies are using cloud for business critical activities. As in, you can't take orders if you can't access your salesforce.com service or maybe you have cooperating colleagues in different parts of the planet that are using a shared storage system, right? And they can't cooperate, they can't do their thing unless they can get access to that infrastructure. So there's great dependence on these cloud-based applications which is clashing with the continued vulnerabilities of the public. So the internet's that's stressing and it's like changing the airplane engine out 35,000 feet. A lot of stuff's going on. What's the bottom line? What are the core issues right now that people are facing? Is it just availability or is it just bad packet movement, bad network design? What's the core issue right now facing that the stress on the internet? You know, it's funny. I work with customers all the time in my daily job. And the number one reason that they come to console connect is for security reasons. It's so funny that every single time it's security reasons. They want to be directly connected to those business critical or mission critical applications. And the reason is clear. If you're directly connected, the shortest path between two points is a straight line, right? So you get better performance and better reliability. Unless the backhoe hits the link and you're dead. No, that's physical connection. So before we get further, I want you to take a minute to explain console connect because we just want to get that out of the way so you can set the context for the conversation. What do you guys do? I know what you do, but share the audience what you do. Yeah, console connect is a cloud and a connection company. We believe that what the internet needs is to have the ability to directly connect to mission critical destinations, whether that be a storage service or an infrastructure as a service company. Maybe it's a particular SaaS application. If you depend on it, if it's business critical, and when I say business critical, what I mean is if it's down for a couple of hours and you can't access it, then your business is adversely impacted. So that's what I call business critical. If it's business critical, you ought to be directly connected because you can mitigate against the concern of not being able to access that particular service. All right, so now you have also two things that you brought as props, white papers. Yeah. Let me just see those for a second. Let's the first one. This one is called cloud connections. And this is a paper I did when I started initially doing some research on how cloud systems work. This is a comparison between the interconnection regimes of AWS, Google Cloud, and Azure. And what I found in the research is that these interconnection mechanisms are completely different from one another. It's so interesting that they not only chose different names for all of their services, but in the case of interconnection for direct connections, they also chose a different model for interconnecting. So for example, Amazon Web Services has what's called Direct Connect. And I talk about how that's set up in both a single and a redundant path to access into your AWS resources. But if you look at Google Cloud's interconnection, they call it Google Cloud Interconnect. And that's really a peering with propagation. It's kind of like peering with somebody but leaking those routes to the other side. So the Google Cloud Interconnect partner is the one who's propagating that essentially BGP peering across the infrastructure. And Azure is completely different. Azure decided that they wanted to have two bundles of three tuple peering relationships. One for private resources you can't access over the internet. One for public, which you can access over the internet and one for Microsoft services. So I laid all this out. So they call that ExpressRoute connectivity provider. I think that's the word you use here. All right, so let's bottom line. We now have four, okay, three major horses on the track. Is there any other ones in here? Or would you just look at the three ones you did? I chose those three because AWS, according to Gartner is whatever, 14 times larger than the next 10 competitors combined. So that's obvious one to put in there. But Google Cloud and Azure are making strong growths. And they have good tech and then they just had their event too. I did watch that network diagram. Amazon does share a lot. James Hamilton shared a lot of information at re-invent. Look, he's so popular. The phones are ringing. You want to grab that? No, that's okay. You sure? You can move on. Just cut on that. Is your wife calling? Probably, yeah. All right, so bottom line here is get the horses on the track. Three horses. Amazon, Google, Azure. Who's better? You know, they're just different. They're just different. Come on, pick one. I think it's really interesting. Pick one, if you were to bet your life on one, which would it be? It depends what resources you need to get access to. It really does. Maslow's hierarchy of needs, go. Google, Amazon, or Azure. I would observe this. I'll get in trouble for saying this, but I would observe that AWS seems to appeal to the broad IT crowd. If you're an engineer, you're like me, you're like the hack code. You might want to play around with the Google Cloud platform. That's pretty neat. And it was designed by engineers so you can see what their mindset was when they designed it. Yeah, and YouTube is not a small operation. Oh no, no, not at all. I mean, it moves a lot of traffic. So Google knows their traffic came. Oh yeah, and of course, massive scale for all these guys. But I also like Azure for dot net types of activities, and of course you can do any workload on any one of these. So what you're saying is that some run great on the dry day, some run okay, and the horses run good on the rain day. So different horses, different courses. Strengths, weaknesses. As Steve Olothay says, horses for courses. But you know what the really interesting thing is, is when you can connect those together. We just announced over at the ITW conference, our cloud nexus product that we couldn't be more excited about. What, to explain that, what does it do? Yeah, it's a mechanism for you to take your availability zones or your regions in one cloud and be able to send traffic through the cloud nexus to get access into another cloud or another region or another availability zone, and do so without having to go all the way back to your corporate data center to exchange that traffic. Got it, so basically not a lot of latency. Not a lot of latency, it's going to be direct, it's not going to be intermixed with other traffic, it's a internet bypass just like our... Okay, what's that other paper you have there? Let's see that one. Yeah, just real quickly, this one's called the Emerging Private Internet. Okay, how to build your own private business ecosystem for business, and by the way, you're the author of both of these, so I'm just going to hold it up there. True private cloud market share is going to be in the billions of dollars, Wikibon just put out a study on that, so hybrid and private clouds are still going to be there heavily with duty, so the notion of private is going to be around, what's this paper find? This is a little bit different, this is in response to the dying attack of April 20, first to 22nd, I forgot which it is. When that attack happened, that took down dozens of very popular websites that depended on that DNS service. And talking with a lot of the folks that were affected, they recognized that in order to not have that problem happen in the future, they're going to have to have direct connections to those mission critical destinations, so no matter what happens in the public internet, their critical interconnections and their critical data paths are still solid and robust. So this is the private side of the internet where you tie down, you essentially lock in connectivity to those mission critical destinations, and the public side is still where you deliver your traffic out to all those who can- Can we get access? Yeah, access to all the routes that could be manipulated and or policy-based manipulated as well. So this is a little bit of a trend now that we're seeing as companies are migrating over to this new platform. I mean, it's like a whole new virtual roadways got to be reconstructed. I mean, I'm fascinated with what you know, we like to geek out on wide area network stuff in the past we have, but to me, I think that whole WAN, wide area network concepts from origination to final destination on the packet path is really complicated with cloud. And now we have multi-cloud. How do you see the routes and then the maps and all the naming, all the addressing, I mean, just evolving to support the one, the capacity? You know, it's an interesting question. I don't think my crystal ball is any better than yours is. Well, you got two good papers here. And I do think we're migrating towards a two halves of the internet, the public internet, which everyone knows and loves and gives you great connectivity globally. But you know that traffic that is attacking somebody else is traversing the same route as the links that your traffic depends on. So I think we're going to see- I want a secure roadways highly patrolled and without bad guys. And it's solid and it's robust. Traffic is not intermingled with others. So your traffic is not impacted by the traffic of others. Console Connect is your company. Had a couple of name changes, but you guys are growing really fast and do a great team by the way. But you're just kind of doing your business and successful. I got to ask you, what's the main reason why people come to you guys besides your awesome technical knowledge and ability to write great white papers and be Dr. Peering, well known in the industry. But seriously, I mean, why are people coming to you right now? Is it because of the alternative? What's the main reason? Yeah, the main reason, as I said before, is security, the fact that any traffic that's being used to de-doss against somebody else is traversing the same routers and links that you depend on. Your traffic, fundamentally in the public internet, is intermingled with other people's traffic. And therefore, your traffic can be impacted by other people's traffic. For the mission critical traffic, you want to have that go across no intermingling elements. So you'd like to have that be directly connected. So security is a number one. Number two and number three kind of go back and forth. It's either better performance or better reliability, depending on what issues that particular customer is facing. All right, Bill Norton, Chief Scientist Console Connect here inside the queue for special coverage of SAP Sapphire 2017. Thanks for watching and stay with us for more after the short break.