 I'm Antonio, I'm an SRE manager here in Copper in Singapore. So I want to talk to you today about how to use Coffler to improve the performance of your web assets. This talk is going to be a little bit high level and we're going to go through all the components from the Copper stack that can help you to achieve that. I believe that on the last meetup, my colleague, Vu, was going through some specific part of our stack, was explaining a specific task, sorry, a specific part. So again, this is going to be a high level talk. I'm going to go through all the components later, we can go deeper into each component if you guys always like. All right, so I started Introducing Coffler with Pond 2010. We have more than 700 employees and counting. We have eight offices and also by the way, we are also hiring. We are hiring SREs and all different roles. We can check our career website. So this is not the topic of the talk. So we're going to go through the real challenge that we have here, which is the highest partations for your website, API. So first off, starting with our infrastructure. So we have more than 150 data centers around the world, including growing. We are provisioning more and more data centers, so with Asia, Europe, America, Africa. So we're going to reach the barrier of 200 pretty soon. We handle more of the 10% of the Internet HTTP request. And we have been in some benchmarks that we speed up each request by 200%. So what are the factors that make the performance critical? The colleagues from the security already mentioned some, but I'm going to go fast over here. So customer expectations are increasing. So we have more and more customers that are dedicated to gaming, other industries that needs higher performance for good user experience. The number of mobile usage has increased a lot as the phones are mobile devices are more basically cheaper. So people can have access to more and more devices. And of course, the number of users on the Internet is growing. So the common challenges that we are facing Internet is facing the websites and the APIs is, of course, slow Internet applications, slow mobile sites and apps. Mobile clients are introducing more and more components being more and more complex. So at the end it has an impact on the user experience usability. So what exactly we are talking about when we say that mobile applications slow? Why this happened? So it can happen for a few number of reasons. One is the number of run trips that you have to establish a connection. Also the number of requests you are sending through APIs or any other source. Also the network throughput, the amount of data per second, and also the size of the payload. This is sometimes very hard since not every type of request is the same, obviously. Also the distance from the client from the origin. This is one of most of the pains since users usually are distributed around the world. We think of the world as a one single, how to say that, how to explain that. So we don't have users centralized anymore. So it doesn't matter where the clients are. So it usually reflects on the time on number one. So a slow pages application API. So business, customers and users, as I said, are globally distributed. The pages are adding more and more multimedia, more videos, more images, more music. So it's obviously more heavy. And this requires not only more, as I said here, more interactivity and personalization, going to more trips back and forth, but all the scenarios that are here. For the mobile, mobile devices have limited computer memory. So this is an additional challenge, making the apps going slow. Also mobile device, connecting to the radio stations. This has a very big impact on latency. Mobile apps and APIs used to increase the calls of an origin. So since the APIs on some specific applications like just gaming, gambling and so on are quite demanding. So business impact, of course, the great brand and the reducing the brand recognition and also lower revenue and higher operational cost. More or less what it seems to happen on the business side. I don't want to go very much into these numbers, going a little bit more into the stack, which is I think more interesting for this meta. So how Cloudflare accelerates your web performance, how the stack looks like. So we, as we said, we have a global network, we have more than 150 data centers around the world. And we use a technology called Anycast. Have you heard about Anycast? So one, not only two persons, three, four, all right, cool. So Anycast is a technology that allows to announce the same IPs all around the world. So if I send a HTTP request on a server to HTTP request from a server in Spain and the origin is in New Zealand, you will get back and Spanish, sorry, you will get root to a Spanish point of presence and your request will get root or internal network until it reaches the origin in New Zealand. How this happened? This happened because same routers can advertise the IPs, same IPs on all our pubs around the world. So you basically traveling to the nearest pub when you send a request. That's what Anycast does. So once you get into our network before, of course, we presently launch our new DNS service, 101.01, and I encourage everyone to use it. It's free. We don't, it's private. We don't keep the source, it will be anonymous, so we don't keep this data. And we also, well, this is for change related. We have a strong presence on China, but maybe for the case it's not that relevant. So our DNS is performing as we test. It's performing better than the Google's 8888, so the latency is lower. So with these two factors, you already get considerable improvement on the performance. Then, so we support, of course, when the requests go in, we support, of course, all the world standards, TLS-13, you know, with the advantages of TLS-13, someone? Those advantages of TLS-13? No? No advantages? Yeah? Yeah? What's the advantage? Yes, less round trips, correct. So it has less round trips, so you are getting performance layer by layer. And then, we recently, well, a few months ago, we launched Workers. Workers is JavaScript, which is embedded on the edge. You can set your own JavaScript on our edge, and it will be served from that. So then, of course, once the request gets into our edge, all your requests can get cash, right? It will be cash. If it's not cash, it will do the whole trip to the origin inside our network, right? So then, after that, we have the web content optimization, which we faster delivery, reducing the payload of a series of images. So we have an algorithm that will reduce the size of the images, and at the end, you will get a game on reducing the payload or reducing the data you are sending over. Then, we have the load balancing, so you can configure different origins for your web servers, for your origin. So we are constantly testing the latency of your origin, so we can send a request to the origin, which is responding faster. And after that, we have Argo, which accelerates the network through the connection. So Argo will find the most fastest route to the origin. I believe that my colleague went into data with Argo. So then, finally, we have Reulgan, who accelerates the content compressing the origin payloads. So with all this stack, it's how we optimize the delivery of the content. Do you have any questions at this point? No? Or shall we leave the questions at the end? Okay, that's fine. I'm going to go fast, since I think we already talked about Argo. So Argo, what basically does is sending the request, trying to avoid congestion on the network. So we have several points of presence. Argo will calculate the latency among all the hops that we have ahead. So it is able to figure it out in a smart way where it can get faster to the origin. So we're going to talk now about the stack with a specific core for mobile. So again, of course, we have the Anycast network route. You get a hit on the closest pop. Then we have recently acquired Nubop, a company that developed a mobile SDK. So we are able to measure the performance and, in fact, getting metrics specific for network devices. Then we have, again, the global network, Anycast. We also have a network in China. The DNS, as we said before, web standard workers. And probably the highlight here for mobile is Ampersand, which use AMB before. Yes? Yes? Okay. All right. Cool. And also mobile contact optimization, which deliver fast images targeting the mobile clients. So it's specifically for mobile. And then at the end, we can add to the stack, of course, wall balancing, Argo and Railgun. So quick summary. So Cloudflare is easy to scale. You are a few clicks away to improve your web performance. You can add more origins. You can personalize absolutely all the settings that you want. You are free to press the button to trigger on and off disabled Cloudflare. And, of course, maybe for another talk, we'll talk more about security. We provide solutions for DDoS attacks of all kinds, level 7, level 4. Yeah. All slow loaders. Any DDoS attack that you can imagine. So yeah. So here are all the components that can make your web assets faster. And yeah. This is a few numbers that, again, we serve HTTP, 10% of HTTP requests. And we serve around 10% of all DNS queries. So it's actually very impressive. Anyway. Thank you. You have any questions? You want to ask? No questions? Yes? WebRTC. WebRTC. What do you mean, WebRTC? WebRTC is our constitutional video app for this year. Yeah. And there are Google addresses. So as far as I know, we are offering a service for streaming. Right James? I think. But I'm not actually aware of how is this working so far. Yeah. So, yeah, I can't go to WebRTC. Sorry, I would. Yeah. We don't actually host anything with the proxy architecture. So we're a matter of minutes. So I don't suspect that. I'm just curious. It's actually very impressive. I'll definitely look it up. Yeah. Okay. Any other question? Yes? I want to ask you something. Allow what? Sorry again. The popular workers has nothing to do with the resolver. Yeah. So, yeah. So how the work, the question is how the workers work. So the workers are a service that was launched like two, three months ago. And you can create your JavaScript code and put it on the edge. And you can use the UI or the API. So you can push your JavaScript code on the edge. So every time that you hit the website using Godfler, this content, this JavaScript will be served. Personally, I use it. We use it. A colleague of mine, if necessary, use it for set, measure the latency that your browser was hitting the server. So you basically created a GIS that it was returning the time that it was connecting. The time of the TCP connection because I think JavaScript doesn't allow you to go through that level. But the time of the HTTP request, I got some nice measurements on depending which pop it was hitting. So it was quite interesting. This is one of the applications. Yeah. You can set any JS code you want. I didn't prepare. But definitely for next time, we can, I think, write this down and prepare a demo for it. Sure. Yeah. Cool. We can talk about that later. Yeah. Sure. Anyone else? More questions? They're running in the browser. The work is. They're running in the browser. You can inject them into the user's browser. Yeah. It was basically, it would request. So the JavaScript code is on the edge. So it will be served from the edge. So you will start choosing the browser, yeah? It executes. You think about it. Yes. I'm not a developer. I'm a network engineer. Historically, there's two places to run JavaScript in the browser that run the server itself. We're now giving you a third place in JavaScript. So for me, the immediate use case is everything you've been on the server side. So perhaps, you know, checking the browser's language now operates now upon. Much closer to the user. So if you want to do a different content to use based on the language, for example, you can do that very close to the user. At least, you know, Geo based on it as well. But I think work is in its infancy. I think our customers are going to teach us all the use cases. So we look, I mean, just last week, we launched, you know, the workers, what we call it, work for the rest of the experience. Yeah. Yeah. Yeah. You know, it's fully functioning JavaScript. Yeah, exactly. So, so it's, yeah, exactly. You know, you can upload your JavaScript code so it can be, so it can be anything, right? Yeah. Yeah. Yeah, we protect about that. Anyway, no more questions? No? All right. So thank you. That's it. Thank you.