 Felly ydych chi'n mynd i'ch gael eu cyfrifio'r symud. Ychydig i ni'n cael ei ystyried i'r ffreddau am y rai ffordd. Mae'r cyfrifio a'n gwneud yn ei ddweud, a'r cyfrifio'n cyfrifio yn ei ddweud, sy'n mynd i fynd i'r cyfrifio sy'n mynd i'ch gael e'i ddweud. A gael ydych chi'n gweithio'r cyfrifio ar y dystau'r ysgol, mae'r cyfrifio rydyn ni wedi'u bod yn ymweld ydweud yn ei brodiogel. So, how can I start talking to people about how relevant we are in this new world when you didn't even know we were relevant in the old world? So, I was asking people, you know, what do you know of Citrix? Most people said, yeah, we understand the Zen kernel, we know about Zen server. Some people say even we use your remote access software so we can access our Windows applications from home. I think about three people this week said, yeah, we use Net Scalar, it's great. No one else even knew about it. So, what I thought I'd start with is give you a bit of background where it came from, what we use it for, why it's a bit different to what you'd know of as a load balancer and then what we're seeing in the market and where we need to, where we feel we need to take our product next. So, we don't really call Net Scalar a load balancer anymore. We refer to it as an ADC, an application delivery controller, something that does a little bit more. And we base our product around four key things. We want to provide availability, we want to increase performance, we want to help offload processing, and we want to be able to add security. And this is mainly around web services, web applications. So, a round availability is pretty simple if we're doing layer four load balancing, what you'd be all familiar with. We do layer seven load balancing so be able to look at what a client is requesting, where they're requesting from, what kind of device they're requesting from or even what's in the request so that we can transfer their request to the right backend piece. We can also balance across geographic locations so it could be that you've got two different data centres, 10 different data centres, it doesn't really matter. But if you've got, you want a single URL and you want to send your users to the nearest most performant data centre for them, we have a global server load balancing built into our availability. So, next piece is performance. How do we make that end user experience that much better? So, we can do this by integrating caching into the device, by compressing data so we can make the payload smaller and we also have some technology we call front-end optimisation. That's something where we actually read the code on the fly. We see an HTML page being delivered. We look at it and we say, the browser doesn't need all that white space so we remove it. We see there's some JavaScript being called so we pull it in, we inline it into that HTML and we send it out so you've got less objects to download, the user gets that data much faster and their experience of using that site or that service goes up. When we try to offload, what we're trying to do is take processing off the back-end. So, in our technology, we're able to offload SSL. That helps you in two ways. One, you can take that workload away from the servers but also it gives you one place to manage an SSL certificate, one place to replace it when it needs renewing. Also, it means you can add extra servers at the back-end without having to deploy certificates across there. The other part, and something that actually was one of the founding technologies within Net Scala is TCP multiplexing. When you think of a big high-performance website, lots of transactions coming through, there's thousands and thousands of TCP connections coming from clients. They hit that the web servers and the web server has to handle that TCP IP stack. All of those requests, very, very fast, opening and closing, it's a huge amount of resource that gets used handling that. So, we've got a very custom TCP IP stack in the box. We're able to handle that processing very efficiently. What we do is we create a permanent set of connections to the back-end servers so that we reuse those and the server never has to open and close those TCP sessions. We're looking at taking up to 40% of the resource utilization off of those back-end services. Finally, security. Everyone finds security important. It should be built into everything we do. So, we have a web application firewall built directly into Net Scala that can be bound on to all of your virtual objects to look after your web services. So, that's the background on Net Scala. That's kind of the 10,000-foot view on it. It has been providing services to e-commerce since 2002. We have huge companies like Amazon using it. Customer number two, I believe, was Google, and they ran it until they developed their own technology. So, a real good pedigree in that space. The way we feel we've been able to do this, we've been able to create a very, very flexible platform is because we believe that networking is done better in software. It gives us the edge over our competition. We don't believe it's our only core differentiation and advantage. And what we believe our core differentiation advantage is the power of any. The fact that we can deliver our technology in any form factor, on any cloud orchestration system, on any public cloud, there is a format that fits. And there's a management tool to run that as well. What we also give you is every single highlighted word you see up here is a choice you have to make. Which form factor do I need? Which type of architecture am I going to build? What we also give you is the power to change your mind, to be able to switch from one to the other without an issue. We do that because we've got a single API, a single code base, a single feature set, and a single management infrastructure to go across all form factors. So, what we really have, and our real differentiator is the power of one to any. So, we've continued to innovate and to give you a bit of history, Citrix, Bort, Net Scaler, incorporate back in 2005. And when we purchased Net Scaler, what we inherited as a technology was a physical load balancer. And at the time that the debate was raging, you can have a fast load balancer. That fast load balancer would be based on custom basics, very much like a switch architecture. Or you could have a flexible load balancer, something where you'd use general purpose processors, very much a software first idea, and then you can write new features quickly, but you couldn't have both. Well, we didn't believe them. And in 2007, we released Net Scaler MPX using multi-core general purpose processors, and we were able to release the fastest load balancer in the marketplace, continuing to have that flexible and feature-rich product. A couple of years later, a new debate was going on. People wanted to take a software load balancer, they wanted to take a virtual machine so they could use it in their private clouds or in public clouds. They wanted to be able to consume dynamic data centres. Because we had a software first model, because we were built on general purpose processors, we were able to create Net Scaler VPX, which is a virtual machine that you can run on the four major hypervisors. So that's Hyper-V, ESX, our own Zen server, and also KVM. As time went on, we started seeing more challenges. And our customers were coming to us and saying, we've got a real problem, we've got so many load balancers in our environment now. We really need to try and consolidate that down, something we like to call appliance sprawl. So they want to bring those all into a single environment. So the one worry we had is if we tried to do this just using virtualization technology, we'd start giving up lots of resources to the virtualization layer. We'd start having network issues because we couldn't push the throughput through those virtual drivers. But what we managed to do using our own Zen server and SRIOV technology is we managed to release Net Scaler SDX and that bypassed the hypervisor layer using SRIOV to get to the network components, to get to things like our SSL chipsets and not pay the virtualization penalty when trying to consolidate down onto a single device. So that brings us to pretty much now, and what next, where are we going next? And I'm sure most of the conversations this week have been around some of these topics, DevOps, microservices, architectures, containers, and it's certainly what we're seeing from our customers out in the field. When we're speaking to people, I've been so surprised at the types of industries that are already building teams or already have teams working in the new agile DevOps fashion, working with containers. Some of the industries that I really thought wouldn't be looking to adopt this until it was far more mature. What that does is it changes the way you start looking at positioning your low balancers and your ADCs. So in the past, a traditional platform would have been an ADC or a low balancer would have sat just like a top of a row switch. Traffic would flow through them very much north to south. Applications would sit behind, you would balance them across. Now when you start working with containers, you might still have an ingress layer where you need to balance to the front end application, but the rest of the microservices are in there, they're talking amongst themselves. Do you really want to come all the way off of your container infrastructure to hit a low balancer to go all the way back in? What we really need is something small that lives within that architecture with inside those container hosts. So that's what Citrix have now released. This is Netscaler CPX. So at the moment we have available a low balancer that sits within a Docker file format. So you can spin these up on any of your Docker hosts. This brings with it some more complexities. In the past we've had physical devices and some of our customers would run tens or hundreds of these very large load balancers. When we gave them the option to start making these a little bit more modular, they got smaller, we needed a way of managing multiple VPXs. We're starting to believe that once this technology gets adopted, there's going to be tens of thousands of tiny micro load balancers scattered across an in a company's environment. And that brings around a problem that we call lots of little. How do you manage lots of little? What we really need is something that's going to not only manage all of these, keep them all in sync, make sure that all their configs live together and make sure they're updated together. It is also that they're in tune with the orchestration that's happening around for the containers as well. So people have started to call and it was Gartner that coined the term bimodal IT and started talking about having mode one and mode two. So the traditional IT being mode one and the more agile IT being mode two. We've got different names for this at Citrix. We call them platform nine and platform 10. Because there's not a battle between these two as to which one's going to win. It's that they need to live together. And what we really want to do is help you find platform nine and three quarters. So how do we bridge this gap? And that is this unified management piece that's going to connect the old and the new. And that for us is Netscale and Maz. So Netscale and Maz, any Spanish in here? No, anyone know what Maz means in Spanish? Means more. So we're trying to give you more, we're trying to do more without our management platform. So the Netscale and Maz, if anyone came to our booth and saw the videos running on Luke, but showing how Netscale and Maz can provision Netscale and CPX across a container environment and could also be driven by events coming from container orchestrations such as Kubernetes and Marathon. So we really build an environment where if you spin up a bunch of replicas of your application in containers, those events will come straight to Maz. Maz will go out and update all the relevant load balancers for you. We'll also, those load balancers will be doing service level monitoring, make sure the application is passing the tests that say it's up and running before they add it in and also remove them when they fail. So just in summary, Netscaler is a lot more than a load balancer. We have it in a number of different file form, a number of different formats, so it can be consumed pretty much anywhere. But also we think we're well positioned to help you in this new container environment. So finally, I'd just like to wrap up by saying we've had to make these changes on the way. We've had to continue to innovate with our technology and we'd like to offer you something. If you could all do me a favour, I'd be really grateful. You go to microlobalancer.com, download your free version of CPX Express before our sales team find out we're giving something away for free. Thank you very much.