 Good afternoon, everybody. It's nice to do this in my home time in leaving Raleigh, North Carolina for almost 20 years now. So Istio, let's do a quick showhand. How many of you are already using microservice on the journey to convert your monolithic application to be microservice-based application? Wow, that's a lot of you. So it's about 50% or maybe 40% of you. So even though a lower number have used Istio, but you guys are definitely looking at microservices. This is a picture we took in San Francisco for our favorite island, Arcturus Island. And we saw the Istio both there. So we were like, we have to take that picture. So what is Istio? Istio is an open service mesh platform to connect, observe, secure, and control your microservices. And what's really neat about Istio, it's an open platform, first of all. It was a project founded by IBM, Google, and Lyft in May last year. And the community has grown into 200 plus contributors. And it's a really surviving community. Red Hat is a big contributor of it, Cisco, VMware, and all the other big companies. And even a couple of startups, too. The service mesh framework is meant to be transparent to your microservices that you don't really have to make much code change to work with your microservices. It's supposed to be language independent, so you don't have to do the things differently for different languages. So how many of you are writing in more than one language? Your team are writing in more than one languages. Okay, so that's a lot of you. So your team is probably having many languages. And some of the common problems, too, how do you connect and observe and secure and control your microservices? I bet you don't want to solve them in language dependent way in your application. So Istio is there to help you. It's a network for services, not for bytes, to abstract that code you need to have in your application, but have the platform provide that code for you. One thing I want to show is Istio is highly configurable, so you can run Istio even without the Envoy sidecar. So many of you heard of Istio. Envoy sidecar has been a key component that runs along with your microservices. But we're saying Istio, if you have a leave service that's not talking to any of the other services, you actually don't need your Envoy sidecar with your services. And you still get a bunch of functionality provided by Istio, such as traffic management, traffic steering, traffic shifting, and fault injection and all that. You can also run Istio with your existing Ingress resource, so Ingress resource controller. So if you prefer Inge Next, you can always start with that. There's no problem with that. You can run Envoy sidecar on your services, still get a benefit of the mesh. One thing I have to highlight, we do say it's very, very, very minimum code changes to your services. In order for you to get distributed tracing to work properly, to tie every single trace together into a single request from multiple of your services, you do have to propagate your headers for distributed tracing. And in addition to that, Istio supports dark launching, canary testing, and for dark launching, we do require you, your application that's to your services kind of propagate the headers for you in this example where it propagates the user header. So these are the partners that help us grow the Istio community, and there's a lot of customers already using Istio in production environment. Some of the big names are eBay, and IBM is also using the weather company being using Trulio. You guys probably heard of it, it's a real estate company. So a lot of company are using Istio in their microservice journey. So I would highly encourage you to try Istio today, and there are some resources you can reach out to us on the mailing list for any questions you have. Thank you.