 Welcome back, this is on the ground in San Francisco. I'm John Furrier with SiliconANGLES theCUBE. I'm here with Owen Garrett, the head of product, Nginix. Here for a special segment to talk about some of the new upcoming releases, HTTP2, HTTP2 is coming out. Give us a take on this going on. Yeah, there's a chunk of technology we're working on for the next major release. And HTTP2 support is going to be one of the biggest developments. HTTP2 is the standardization of a protocol called speedy. It's something that Google and other players pursued as a way to try and make the web faster and more secure. And finally, the standards are getting locked down in the form of HTTP2. Browsers are beginning to support it and server applications like Nginx are adding in support. It's funny how we get here in this market. You know, everyone does stupid DNS tricks, all these hacks to make things secure because the growth has been significant. The web scale companies have built their own. So talk about the implications of the standard that just got set and what's coming out in the new release. Sure, so the standard is a complex standard. It's not just a drop in replacement. It requires a lot of engineering. Requires some very, very high quality code to make sure that it's implemented efficiently, effectively and securely. It depends really heavily on SSL for security. That will become a standard for all HTTP2 traffic. And these are areas that we've got a lot of track record in. We've been building this for a technology for many years and we're determined to build out a fantastic high performance, drop in easy to manage solution, so that you can layer HTTP2 on the front of your applications, your APIs, your websites, so that your users can get the confidence that standard's in place. You can stay at the front of technology as it continues to innovate. And we intend to deliver the gateway technology that you need to do that. So take me through this. I want to do a drill down because my mind's spinning. It seems really, really hard to the customer. So thinking with tokens and kind of siloed applications after the run on top of open standards like HTTP and HBS, it seems like a lot of hassle for the customer to go out and update all their apps. It just scares me just to think about, I got this working now. Why would I do this? Why would I go to this next rep? And why should I do it? It seems harder. Yeah, the pace of change in the industry is really quick in the last few years. HTTP itself is a pretty old standard night, over 20 years and for years people have developed tricks and techniques to work around some of the limitations of that standard. HTTP too is an attempt to try and productize that. It's a new layer on top of HTTP that deals with some of the performance issues that are inherent with HTTP. Why would I deploy it on my customer? So if you want to deploy that, if you're getting demand from your end users, they want the security of knowing that your site is running on a secure platform. They want to know that you're delivering the best possible performance. One of the main benefits of HTTP too is the way that clients can send requests to the server. They can ask for things in a much more efficient way. So over in many circumstances, you'll get better performance, faster websites, less delay and there's a really strong correlation between the speed of a website and the amount of time that a user spends on that site and that time often ends up in greater transactions, greater advertising revenue, whatever the KPIs are for your site, performance is something which will help to influence. So let me try to understand this. So if I'm running like Node.js at the edge and I'm running a lot of stuff on the browser, I got memory problems, is that related to this stuff? Is this the right profile customer that would need this? That's the right kind of profile customer. But our approach for HTTP too will be to layer that in front of your Node.js application. You don't need to tweak the application to support HTTP too. You need to put an HTTP2 gateway, a translator in front. That's exactly what we do now for SSL, for speedy. It's a common pattern, well understood and we're extending the product so we'll also be able to do the same for HTTP2. So basically it's nondescriptive to the operations to the customers that you guys have. That's our goal. There's a lot of concern in the industry but higher enterprises gonna move from their current architecture to one that supports HTTP2. And our goal is to provide the tools and to make that transition as easy as possible for them. How big is this gonna be HTTP2? I mean it sounds awesome, we need more security. That's the number one thing people are worried about. Identity theft, losing their credit cards, it's happening all the time, fraud is huge. Obviously big data will help that which is another DevOps movement. But how big will this be in your personal opinion? It's gonna be a significant bit of technology. It's gonna be something that you will need to support as a website operator in order to stay relevant and to stay current. You can't measure the size of the technology. We can make predictions about the adoption. But you feel good about this, it's pretty critical. But it's an important thing to support. It shows the direction that the industry is going in. It's critical infrastructure, HTTP and rounding all the protocol. So we'll be here about this at developer conference in September here in San Francisco. Yep, there's a lot of updates coming at our user conference. So not just around HTTP2, there's a number of other innovations we've got in the product and we're gonna be releasing or showcasing those in September. We're gonna get information on this NGINX website. What are some of the location, URLs, Twitter handles, web addresses? Yeah, come and hit the website, NGINX.com. You'll see as we open, we already have a call for papers. As we open it up for registration, you'll see it advertised through there through NGINX.org, you won't miss it. Oh and Garrett, head of product here in San Francisco, we're on the ground. I'm John Furrier, thanks for watching. Special CUBE conversation on the ground in San Francisco. Thanks for watching.