All right, good afternoon, everybody. I'm glad you joined us for the afternoon NAP session. I would be napping right now if I wasn't giving a talk, because I don't know, lunch does that to you. And it's like the last day of the conference. Well, thanks for coming to our talk. My name's Jeremy, and this is Todd. We'll introduce ourselves a little bit more, but we're going to be talking all about NAPs.  We're actually going to play with NAPs together. And hopefully, we'll get everybody connected in the room. So we'll do some quick intros. My name's Jeremy. I'm a long time gopher, and so I like write and go. I'm a developer, and I've worked in a ton of different industries. But I've also worked on a lot of projects in the Go community. So if there are any gophers in the crowd, you might recognize some of these projects. And currently, I'm working at a company called Sinadia, where we maintain the NAPs project, which is a CNCF project. There's also a lot of CNCF projects that use NAPs under the hood, which is great. So I'm sure you can go to the floor and see a bunch of different projects like Cosmonic and Intuit with a lot of their projects using NAPs under the hood. I recently moved back to engineering from a big product role that I was in for six years because I just missed building things. And so I'm really glad to be here and talking with you guys about NAPs, because not only is it a really fun technology to talk about, it's also a really fun technology to demo. So we're going to have a lot of fun today. Todd, you want to introduce yourself? Sure, yeah, thanks for everybody for being here. So yeah, Todd Beats, long time messaging and services and all the things in big enterprises, being an architect, high tech, retail, and with Sinadia for about a year where I get to indulge in my passion for NAPs, which is really exciting. Awesome, awesome. So friends, NAPs is an adaptive technology and we'll go more into that. But so is this talk, because I didn't know what to do for KubeCon, there's probably plenty of you that are using NAPs in production. I don't want you to raise your hands.  Go to this URL right over here. I'll give you guys just like a minute to go do that. It's going to have you fill out your name. If you do not want to be somewhat featured in this presentation, then don't just fill out a random handle or whatever, don't fill it out at all. But this is going to be our fun kind of audience participation part of the talk and we'll roll through it throughout the talk. So go to kubecon22.fercel.app. I'm going to roll on over here as well. You should see a screen like this. I'm going to put my name in here, Jeremy. I'm just going to fill out a couple of questions. This is going to be kind of our roadmap for the talk. I only have 35 minutes and I have way too many slides. So we're going to pick a subset of them and go through them based on where you guys are at as an audience. So I'm using NAPs in production. I probably want to hear about microservice architectures. And obviously the most important question, who is more likely to win an arm-belting match, is Jeremy, let's hope. All right, cool. So we have some results coming in, which is great to an overwhelming amount of folks who are here and have never heard of NAPs before, which is great. We're going to talk a lot about what NAPs is and how to use it. And it actually seems like a lot of people are interested in NAPs for microservices architectures, which is fantastic. We've been seeing this trend happening a lot with the companies that we've been working with that are using NAPs. And there's a lot of really cool tools, some that you just can't do with technologies, most technologies today. It looks like it's pretty close, wow, pretty close tie in the arm-belting match, but Todd is kind of inching ahead. We'll see what happens by the end of this conversation that we're having together. You guys will also see that there's some logs. We sent your survey information. This is all built on NAPs, by the way. NAPs isn't a front-end framework, of course. I'm using React and all kinds of other stuff over here. But a lot of this information stuff is built on NAPs. We're going to dive in and kind of check out this data that we just generated for ourselves. Before we do that, let's just talk a little bit about NAPs, since we have a bunch of newbies in the room. So at Senedia and at the core of the NAPs project and its design is this idea about rethinking connectivity. Meaning we get to rethink, or what would the world look like if we rethought some of the core fundamentals about what it means for machines to talk to each other and what it means for users to interact with machines. And if we rethought that, what kind of new tooling and ideas would come out of it. And so I want you guys to come into this with an open mind and know that there's maybe some new types of solutions and new types of thinking that we can adopt in order to connect everything better. And so multi-cloud and Edge, which has obviously been a huge topic here at this KubeCon, is really driving a massive transformation. And I want to talk about some of the ways that our current solutions don't really live up to some of the challenges that we have because our expectations are changing of where our data should be, of where our compute should be, being closer to who needs it. And that's basically the whole theme around Edge. And there's a whole ton of new problems that kind of come with that, where we're now going, okay, we have this big thing in our cloud, we've kind of figured that out or we've kind of gotten used to what that looks like. And now Edge is creating some new problems. So some of the limitations of today's technology is that we use DNS and host names in IP to discover machines, right? And because of that, we have kind of these one-to-one communication patterns. And for the most part, if we're using things like HTTP, we're doing this kind of like pull-based requests and reply semantics. Sure, we have some other technologies that are doing some streaming and some push and everything like that, but it's more layers on top of the same thing. We also have adopted this kind of perimeter-based security. Hey, I'm gonna just throw all my stuff in like a VPC and everything will be okay. And I think many of us who have done that have learned that there's actually new problems that come with that, especially when you're gonna go outside of the scope of your VPC, whether it's for policy reasons, whether it's for partnership reasons, or whether it just makes sense to be able to have separate networks in those cases. We've also gotten so used to location-dependent backends, right? Our typical kind of cloud approach is to say, cool, we have these horizontally scalable stateless services and then a centralized like database or backend to that. And as soon as you try to spread some of these stateless services closer to the requester, now you have the problem of latency back to the actual database or data store itself. And so these are some new problems that we have to solve when we start moving our compute. We also have to consider what does it look like for us to move and distribute our data. And again, all of this stuff is kind of built on this like HTTP one-to-one communication, making the assumption that machines can only talk to each other directly, right? It's almost like we have cell phones today and I can go out on Twitter and I could say, Twitter's kind of like this town hall where I can say, hey, I'm putting something out into the world. Whoever's interested, who's ever subscribed to me can go see that information and do what they want with it. But in a lot of ways, these technologies are kind of stuck back with phones and address books. And me remembering what people's phone numbers are, looking up in an address book and calling them one by one. No group calls, no Zoom, no more like collaboration, just one-to-one. So this is where I want to introduce NATS, right? So what is NATS? Now this can't be a KubeCon without a buzzword soup paragraph here. So NATS is an open source, high performance messaging system and connective fabric. And really what the project aims to do is to simplify the number of technologies that you use for your services to communicate, all while empowering you to build systems that are globally available, multi-cloud, multi-GO and highly adapted to change and scale. Now I know that seems like a lot, but what we've actually done with NATS is really hone in on what it looks like to communicate. We're not trying to handle orchestration or compute. A lot of those are solved problems and a lot of you guys have already adopted much of that. But we want to handle the communication bit, which we think gets kind of thrown under the rug a little bit and not really discussed. Okay, so what does NATS do? Well, one of the things that it solves for is this idea of location independent addressing, meaning you don't use DNS, you don't use IP addresses to be able to have your services communicate with each other, right? We can now use these kind of subject strings which I'll show you in a sec and they can communicate with each other and not have to know where these particular services are in the world. We also introduced this idea or we've implemented this longstanding idea of end-to-end communications, meaning we're not just necessarily talking about one-to-one, but the flexibility of everything in between, everything talking to everything and everything talking to some things. And I'll show you how that's kind of expressed inside of NATS. We are also push and pull based. So somebody can go request data, ask a question and get an answer back or they can have something pushed to them. I'm interested in a particular topic and I want that pushed to me. We also have this idea of decentralized and secure multi-tenancy. So we really wanted to design NATS to be truly multi-tenant, meaning that completely different organizations can coexist on a single NATS system and still have their security requirements met. And this works really, really well for organizations where you don't have to necessarily tune your NATS deployment to your specific use case. You deploy NATS in one way and it works for all sorts of different use cases, all sorts of different tenants that can do whatever they want. And lastly, and we'll touch on this a lot more, is this idea of intelligent persistence that if we store our messages in a globally ordered set of messages, we can actually do some very interesting things around how we replicate those across the globe and how we express different types of data structures, high level on top of that, things like key value stores and object stores, all from this atomic unit of a message being stored and persisted. Lastly, NATS operates very easily, mind you, on a global scale, meaning that you can run in multiple clouds, you can run in multiple data centers, multiple regions, and have all these things connected and acting as one system, punching through all these kinds of different networks in your public clouds, extending all the way to the edge where you can run this thing on a Raspberry Pi Zero and be able to have that operate as a single large organism. We have customers doing all kinds of really awesome things from constellations of leaf nodes and all kinds of crazy stuff to solve problems at the edge, and that just kind of proves out that NATS has this global scale that is actually not too bad to set up. Okay, so on the more practical side, before I kind of show you guys what NATS is, NATS is a simple client server architecture, meaning we have a NAT server that you pull up, that you can cluster and super cluster and all kinds of fun stuff, and that's written in Go, it's really easy to deploy, we have containers, we support Kubernetes, obviously, but we also support putting it on bare metal if you really wanted to. It's really about the flexibility here. And then on the client side, you can't solve for a big communication problem unless you support a bunch of different languages. So we have 40 plus client libraries to work in in all of the major languages that people use to then connect to NATS. So I wanted to show you guys kind of a NATS core demo and what it is. Again, I said NATS is really fun and easy to demo, and let's hope that that's true. We're gonna pray to the demo gods for a second and see if this conference wifi can really work it. So it looks like Todd's still, well, no, it looks like I've inched out Todd a little bit on the arm wrestling match. That's great. So let's go over what NATS core is. So NATS core is basic fire and forget message publishing. We actually have a CLI that we've built and go called NATS where you can interact with a NATS server as a client. And this is really fun for doing POCs and just kind of showing you the attributes of how NATS works. Now, can everybody see that all right? Are we good? Okay, I don't have to put out another survey if you can see the screen or anything. Okay. So the way NATS works is right now I have default context, which means I have to fire up a NATS server. NATS server is very hard to fire up. You just type NATS server and you get it running. Now to interact with the NATS server, NATS has kind of this core atomic unit of a message and you can publish and subscribe to these messages. But you could also do other patterns like request, reply, fan in, fan out, message persistence and streaming. So I'm gonna show you guys what it looks like to subscribe to a message. I'm just gonna say hello.star. This is subject-based addressing, meaning the star is a wild card for that particular token. And so I could put anything I want in there, but it's going to match to that particular subject. And then I'm going to reply, or I'm not gonna reply to anything. I'm just gonna subscribe to the hello subject.  Count, I don't know, 1000.  Now payloads in NATS is anything that you want to send to that message. And it could be anything, we're payload agnostic, meaning this could be a string, it could be JSON, Bson, Proto, whatever really you want, whatever kind of suits your fancy. We have no opinions about what the data format is. So I could send 1000 messages and it's actually pretty quick. To show you guys kind of the speed of NATS, because I say it's high performance, but I guess you could say anything's high performance nowadays, but we have a NATS bench command and I could say I want one subscriber and I want one publisher and I want to send it to the hello subject and messages and to get a good sample size. I think it might need one more zero. I don't know, that was too fast. Let's put another zero on there. There we go, okay. So as you guys can see, we're publishing, this is locally on my M1 MacBook, but it's 7.3 messages a second. It's pretty good. And again, you can cluster these for slightly more performance and everything and durability and things like that. NATS also has this idea of request reply. So I can say NATS reply, let me get rid of this, NATS reply to hello.star again. This time I'm just going to say reply with an echo, but I could reply with whatever I wanted to. This is kind of your typical HTTP request reply if you can think about that. And then I could say NATS request hello.jeremy and pass in a payload hi. And you could see I get a response back. And so even though this is all kind of pub sub under the hood and this is all asynchronous communication, you also get these very easy semantics both in the client SDKs and inside of the CLI to be able to build little bits of microservices on this because now you kind of have this mixed pattern development, which we'll talk about in a sec on when it comes to microservices. So that's kind of a high level demo of NATS core. Now let's jump into why NATS is good for microservices and then we'll close out with some NATS JetStream just because it's really cool. And I want everybody who's developing microservices to be able to kind of adopt something like a durable message queue or persistence or anything like that. Actually, before we move on from NATS core, does everybody still have their window up?  Everybody whoop your phone or laptop out again, we'll have some fun here. So I'm gonna say NATS context select. You guys were all interacting with a NATS server in Austin, Texas, it's our demo server. So I'm going to actually log into this demo server and I'm gonna say just to kind of show you guys one more thing which is this kind of idea of queue groups and load balancing and everything like that as well as M2N communication. So I'm going to quickly say NATSCubeCon.rollcall and I'll publish that. And I'm gonna say replies, say how many replies I'm expecting back. Now, HTTP can't really do this. They can't say give me an endpoint and then give me all the people who care about this endpoint. That's just not how it works, right? But an M2N communication, you can. When you guys are logged into that, you're actually subscribed to this topic. And I can say zero and I'll just wait for a timeout. Whoops, what did I do wrong? Let's see. Let's go over here. See what I did wrong. Oh yeah, whoops, NATSCubeCon.rollcall, thank you, NATSCubeCon.request. CubeCon.rollcall, reply zero. Look it, I got everybody's name. Some people more than once. But yeah, everybody's name in here, which is pretty cool.  I can go do that again just to show you guys, but we have a lot of people in the room that are logged in, which is pretty cool. And because it's going through that demo server, that's why you see that RTT is at like, sometimes one second, sometimes a millisecond. But if a NATS server is very close to you and this is the perfect example of what it looks like to be at the edge, these would actually be very much sub millisecond response times. I could do one more. Let's do an idea of load balancing. So you guys are all still subscribed to the same subject, but I want to load balance it between all of you guys.  I could say kubecon.lottery, because I only want one person, but I want it randomly chosen. I'm gonna get rid of this reply. We're gonna say, okay, M, whoever M is that's in the room, won the lottery. What do you see on your screen? You don't have to raise your hand or anything like that, but hopefully some confetti should fall from the screen. Congratulations, you've won the NATS lottery. Awesome. Cool, so that is a high-level overview of NATS, let's get back into NATS for microservices. So just as a high-level overview again of NATS core, fire and forget message publishing, it's really fast. We all saw that in the bench. And this idea of flexible subject-based addressing with wildcards, being able to kind of MUX and all of your different subjects and create a subject hierarchy that makes it really great for being able to discover what you need to do with that data. And again, payload agnostic. So whatever format you want to use, I just threw strings around here, but you could use whatever kind of format you want. As far as this kind of like multi-pattern approach, we support that request reply, publish and subscribe, fan in and fan out for typical pub sub, and then this load balancing, like I just said with the lottery, you have free load balancing via this idea called Q-groups. Okay, so now let's choose your adventure time and since everybody was interested in microservice architectures, let's talk a little bit about that. Now, when I think about what makes a good architecture, you know, when I was a developer, it almost always seemed to be like, oh yeah, it needed to be extensible, we needed to be able to maintain it, but there's all these other properties that really matter. And I feel like this resonates a lot with the Kubernetes and CNCF crew, is that there's so much more to application development and architectures than just making it maintainable, making it resilient and secure, observable, extensible and adaptive to change. And I wanna talk a little bit about how NAT approaches each of these. So in terms of resilience, we talked about this client server architecture. The coolest part is, and I didn't demo this, I really should have, but clients self-heal, meaning if a server goes offline, especially if you're in a clustered mode, the client already knows about the server's peers and automatically connects to that peer. It's done so very transparently for you. We actually fail over like entire clusters as well. I wish I had a million minutes for a demo, but I can't. I probably could show you guys at some point, if you come up to me or anything like that, how we fail over entire clusters. Like if an entire region goes down, all those clients move over automatically to the closest region based off of RTT. And that's just something that NAT's handles automatically for you. Servers also protect themselves at all costs. One of the challenges with building messaging systems is having bad, not bad actors, but slow consumers that eat up all of your resources. And so NAT servers are really trying to be a messaging server that protects itself at all costs to keep resiliency up. So it'll boot out slow applications, which we think is actually a really good trade-off because we don't want to eat up too many resources on the server side. Like I said, failover is automatic and load balancing comes for free. What about this idea of security? Well, we've created a security model in NAT that's what we call decentralized, meaning that we use some cryptography to be able to verify a trust chain, which means there's very little that needs to exist on the server. We don't store any private keys or anything like that. And we isolate these NAT's environments via accounts. So you can have an entire NAT's cluster for your organization, have multiple teams on that cluster, doing whatever the heck they want in their world, but also having the ability to send data over account boundaries, which is great. So sharing the ideas of streams and persistent streams and services between accounts, also enforcing resource limits for tenants. So very much in the world of Kubernetes saying, we want to operate this Kubernetes cluster as kind of a public utility for our organization, you can do the same with your NAT's cluster. And creating permissions for each service without server changes, which is really, really cool. So again, this is all cryptographically defined. You're able to mint a JWT that you just give to somebody and they can then have a secure way of using exactly what you want them to use without having to make any updates to some server user database or anything like that. Let's talk about location transparency. I talked about this a little bit inside of our, when we were talking about our subjects, but location transparency is a key characteristic of service oriented architectures. This is kind of where it came up with, when SOA was all the rage, the idea of location transparency really got big. But it's this idea of temporal decoupling and that consumers of a service don't really know what a service's location is until they locate it in a registry. So the ability to kind of have a late binding to a service without knowing its address or anything like that. And it gives you this flexibility that allows you to kind of swap out services, rebalance traffic, everything like that. All the things that you've really liked about a load balancer, but just baked into the construct itself. So because we have location transparency, you get free service discovery with subject-based addressing. You can easily move services between cloud providers given that they're stateless and they just kind of really care about NATs. And you automatically get routed to the closest responder. So if I'm asking a question on a particular topic and I'm over here in Detroit and the person who is closest to me is all the way in California, I'll get routed to that. But then if I stand up a service that's maybe in Ohio, I will automatically start getting responses from NAT service. I don't have to do any more reconfiguration. NAT handles all that for me as a broker. You also get this idea of traffic shaping and subject mapping, which I don't have time to cover, but it's a way for us to configure splitting traffic to different weights or rerouting traffic, which is great for like rollouts, betas, and being able to test things. Let's talk about observability. I might show this in a little while, but you can observe all traffic in real time. NAT says just a message broker. So I could say, I want to subscribe to everything. Give me everything, and then I can go put that in a data store somewhere, put it in a stream, and eventually transform it into something that's like Prometheus compatible, which we actually can do with a tool that we've created called Surveyor. So you can gather things like latency metrics on each of your services, which is really, really neat. And you could filter all these metrics, again, via Subject. So we're taking some of these constructs, like some of these atomic units, like Subject-based addressing, and we're kind of putting it everywhere. Like what if you could do your metrics this way and your observability this way? What if you could do your services this way or your streams? And so we're really trying to stretch a lot of the basic concepts of this into something that makes a lot more sense as a whole. We also have this idea in terms of extensibility of this like multi-pattern development. So again, our synchronous request reply, and then our asynchronous patterns of publish and subscribe. And if you want to persist your data, or you want to be able to catch up with your data, or you want to be able to do something like service mesh does, where it's auto-retries, you could do all of that with being able to persist those messages and create a policy that works for your particular use case, which is awesome. So I haven't talked about JetStream yet, but you also have the ability to create things like key values and object stores. I can be a nerd and talk about NATs all day long, but this is kind of what I think about when I think about NATs for microservice architectures. We want to really stretch beyond just request reply and going through proxies for everything to talk to each other, and instead say, can we embrace more patterns? And instead of saying, well, on the back end, we have this kind of persistent message bus, and on the front end, we just do GRPC everywhere. What if we mixed some of those, and we really tried to pull things off the shelf and use one system to broker all of this information? How much better would something like collecting observability metrics be? Okay, so I don't have time to look through all of these other slides, because that's not what we picked. But there's one thing that I want to close with, and then we can move on to questions, because I'm sure, I hope, some of you guys have some questions. So let's talk a little bit about JetStream. So NATs JetStream is a next-gen persistence layer that's built on top of NATs, and it allows you to have this temporal decoupling between publishers and subscribers, which basically means that if I'm publishing a message, that subscriber doesn't need to be online in order for the subscriber to eventually get it. And the way we solve that is by persisting the message, either in memory or on disk. Many of you who have used solutions like Kafka know very much all of the fun challenges that come with being able to do this at scale. One of the cool things about NATs is by default, it is globally scalable. So we get to piggyback off of a lot of the attributes that Core NATs brings us to be able to bring us this type of multi-tenant persistence. And so instead of talking to you guys about what JetStream is, I want to show you guys what JetStream is. And so you guys can visit this. NATs whiteboard.onrender.com room is kubcon22. If you guys are also staying on that page, I'll just navigate it to you automatically. If I can, let's see. I'll navigate you with NATs. Let's try that. So I will say NATs. See, I'm in demo. I'm gonna say NATs kubcon.navignavigate. And I'll paste this in. Nope, NATs. Pub. I don't remember that. There we go. Some of you guys should be already moved over there by now. Feel free to draw on this little whiteboard that we have. I want to see everybody's beautiful drawings. Here we go, cool, awesome. Now, the fun part about this is this is all in JetStream, meaning it's all persisted. You can refresh the page and it will load it all up again. This is again using our demo server in the whiteboard, but, sorry, our demo server in Texas. But one thing I can do is, like I said, I can say NATs sub and I can subscribe to this whole stream. I'm going to say, I think this is called whiteboard, or let's see, stream whiteboard. And this could give me all of the rooms. I don't want all of the rooms. So I can filter on that subject. I'd say whiteboard.cubecon22. I think that's what I called it. See how it works. That's pulling in all of the data locally for me. So I could put this on a local stream. I could replicate it into a different cluster or into a different leaf node. I wish I could talk about all of those things, but we're running out of time. But as you can see, I'm getting your guys drawings in real time as well, which is really cool. And this is kind of the ability to observe state. I'm pulling from a stream right now so I can kick it off and I can start it back at the beginning and recreate everything. Or you could just say, give me whatever's happening in real time. It doesn't really matter. There's a lot of options here, but as you could see, we're kind of graduating from this kind of core notion of what does it look like to just send a message around and then what does it look like to do that at scale? And now what does it look like to store those things at scale? And that's the very basics of NAT. So I hope you guys had fun drawing over this fun conference Wi-Fi. Of course, if I brought a server over here closer, we'd have much better performance, but it looks like some people are also deleting, which is great. So anyway, thank you guys so much for the time. I know we have about five minutes and I wanted to make sure I can answer any questions. So thank you so much. My beautiful co-host Todd will hand out mics to anybody who has questions. So this solution kind of falls within a whole bunch of actual other solutions that are out there. You mentioned Kafka. This does somewhat what Kafka does, right? I see some of the things you can do with Redis. It falls into that, right? MQTT protocol is almost identical to this. Where do you see NATs in that whole range? I mean, why would I use NATs over, say, Kafka? Yeah, so one of the big reasons we have folks adopting NATs, especially at the Edge, is because they have to put it on smaller and smaller devices. Who wants to run Kafka in 10,000 Raspberry Pi-like devices? They're gonna have a bad time. That's usually what we're seeing. So because NATs is small and it can run on very low resources, we're seeing that that use case is really great. And that's starting to expand to not just the Edge, but in places where often I see companies that are still using Kafka on the very back end, but having a scale Kafka like multi-Geo, multi-Cloud, everything like that is a challenge. So I'll often see them using NATs kind of on the front end of their stack and maybe putting it still in Kafka because they have a big legacy of data processing pipeline that they don't want to get rid of. But quite often, NATs is like for that scale. Okay, thank you. One other quick question. Common use case that at least I see in MSA development is a request queue. So publish a request and I got a gazillion subscribers, but I only want one subscriber to actually actively work that request. How do you do that in NATs? Yeah, so using streams, we have a concept called a work queue stream which is very much like just a durable queue and one thing picks it off at a time. Under the hood, they still use one consumer to kind of keep track of it, but multiple subscribers can interact with it. And so it's just a type that you configure. I didn't get to show how configurable streams are, but we have a really cool stream and consumer architecture that works really, really well for a bunch of different situations. So whether you're just trying to do retries or you're trying to do a big durable queue that scales or you're trying to put a key value store all over the world that responds under 10 milliseconds. Like you do all of that with the same kind of construct, just kind of tune differently. Yes. Yeah, we are using in NATs today. So how does it load balance if you are using a Kubernetes node board? Yeah, and so the question was, how do we load balance when we're using a Kubernetes node pool? Well, the fact of the matter is we're, so each one of those pods essentially would be a client that subscribes to a NAT instance, and NATs will be doing the load balancing. And so since NATs is getting the message and essentially brokering it for request reply, you get all of that load balancing for free. Okay, and one more. So do we have any maximum, or is there any TPS the NATs were able to support? What is the maximum TPS, yeah? That's highly dependent on your use case and everything like that, but what I like to say is, NATs easily pushes like 60 gigabit, or floods 60 gigabit links if you want it to, especially for Core NATs. On a per stream basis, we're seeing a lot of people get about like 250, 300,000 messages per second persisted and that gets punched down to the disk for every message. And, but for Core NATs for just like request reply, stuff that's not being persisted, I just benched it on my M1, it was like 7.1 million messages a second. I'm sure on Beef Your Hardware, you can push a lot more. Yeah, over here. Hi, my question is how message replay works? So what I mean is if subscriber is down, and then it comes back up. Is it ordered like Kafka or? Yeah, so you can order it. We also have a similar concept to like ordered partitions in Kafka, just slightly different, but same basic concept. But you, that's not out of the box, so you don't have to adopt that complexity if you don't want to. But you can configure a lot of what retries look like for messages. You have a retry window that you can configure on a per consumer basis, as well as a back off policy. So if you wanted to like actually manually configure per consumer, what kind of back off policy you get and how many retries you allow it to, then that's pretty easy to do. We also get this question a lot, like do you have a dead letter queue? We don't officially support a dead letter queue, but we do have advisories for when something maxes out on it, it's retries, so you can easily create your own dead letter queue. Part of the NETS philosophy is like, we wanna create a lot of these constructs, but we don't want to like adopt too much tech debt in the stack, so it feels like you're adopting a ton of stuff that you don't need. But it's easily to create one of those, yeah. So it's been compared to Kafka a lot, so what I, of course I have to ask is if there's any migration plan from using Kafka to using NETS, like any sort of automation that's been done to kind of streamline that migration, or is this like maybe a bit too difficult and more suited if you just have a greenfield project? Yeah, that's a great question, and so we do have a NETS Kafka connector, so you can kind of draw the line on where you wanna pick up some of the applications that are using NETS, and then some that are still using Kafka, and that's kind of where we try to guide people who are doing it either, they're replacing Kafka in a lot of ways, but there might be Kafka still living somewhere, and that's where we use that connector. We have one question over here. Over here? Oh, okay. Yeah, it could have. Yep. Yeah, I wrote that little React demo on the plane. It's actually super easy to write, it's like a hundred lines of React, and so it, but you're right. So as far as like exactly once guarantees, we do support that. So we support a bunch of different qualities of service and exactly once, obviously comes with a lot of trade-offs as well, because it involves a lot of acknowledge, acting and macking, and making sure the message really does get through, but that's all pretty easy to set up on when you're configuring a stream and its consumer. And by the way, we divorced streams and consumers a little bit from each other, so you can set up a stream and have like exactly once delivery for this consumer of this stream over here, and a different quality of service for this kind of, this consumer over here, and it's all still the same data set, which is really neat. Yes. So earlier you did like a navigate and a couple of other requests that you sent. Were those handled by like the React app that you wrote, or are they built in like the SDK stuff that handles this from that? Yeah, so those are all, that was just part of the React app. So I just, it's a very easy subscribe to this topic and then go do something. The client applications are very easy to write. If you're used to writing like anything, any sort of web application with handlers, it's very similar to that. Yeah, it's very easy to build reactive applications in that way. All right, I think we are at time. Feel free to come up to me if you guys have any more questions. I love talking about this stuff, but thank you so much for attending. Really appreciate it.


and also also member countries. Distinguished ambassadors and heirs of delegations, dear delegates and participants, invited guests and members of the media, good morning to all of you. It's my pleasure to deliver the open speech of this third extraordinary conference. The first extraordinary conference was held in Bern in Switzerland in 1900, and after more than 100 years, the second one was held only last year in Venezuela. Now, one short year later, we are holding our third extraordinary conference. This congress, held in short succession, affirms the role and relevance of this organization and reflect the pace of business today. Business and no longer wait. The model of holding quite renewable congress is for all decision making has not always shown itself to be in support to get the demands of the 10th first center. Recent times have highlighted the union's need to move quickly, solve the many challenges of the union, and to grasp its numerous opportunities. Ladies and gentlemen, I think I can say without risk of embarrassment that this is one of the most important meetings in the Universal Postal Union's 145 years history. We have come together here in Geneva to decide on one person, and one question more, the issue of immigration rates for the EU. Before going further, let me say that over the years, since the production of the immigration system at our World Postal Congress in Tokyo in 1969, we have recognized the system is not fit for battles, but could not be fixed overnight. Over the long years, other countries have striven at successful processes to refine and improve the rates for the prevailing business trends and models. In Istanbul in 2016, I have thought the consensus has been found, as well as an acceptable, time-lapse timetable for introducing fair rates. It is therefore regrettable that the new rates will not come soon enough to prevent the necessity of holding this extraordinary Congress. As you have that, I have deep respect for the Syrian and the sovereign right of the member countries to express their views and reach sensible solutions, no matter how difficult the terrain of uncomfortable necessities. The U.P.U.'s purpose has always been to create a forum, invite member countries, and encourage the necessary discussions to transform and empower our industry. I also feel, however, a fond sense of duty as a director general of the U.P.U. to speak out on behalf of the integrity of the international postal network. The U.P.U. is powered by the U.P.U. to service organization. The duty to ensure that everyone on this planet has access to international mail. Allow me to quote from the scope and objectives of the constitutions of the U.P.U. that came to force in 1875. When it first came to force, I quote, the countries adopting this constitution shall comprise, under the title of the U.P.U., a single post of territory for the simple exchange of letter post-mortem. Freedom of transit shall be guaranteed throughout the entire territory of the union. End of quote. And again, I quote, the aim of the union shall be to secure the organization and improvement of the postal services and to promote in this sphere the development of international collaboration. End of quote. This position is true. Today, as close in 1875, and for the 100 for five years, the U.P.U. has done foreign phrases, single post of territory, freedom of transit, guarantee throughout the entire territory or the development of international collaboration. I choose this one to remind us of the very reason for our existence as a union. Our meeting today is about the postal regression rates, but it's also about all of us choosing the right path for our union. The right path to protecting the integrity of the universal service application. The right path for all member countries and their sustained postal development. And the right path to prosperity for this industry. I believe we are at a crossroad where a choice is made and valid way and set the course for the rest of this century. As with all such paths, once decided, the union may never be able to address these steps. The first step on this path will inevitably lead to the next and the next until the road taken becomes the only road. I say to you that the initial step by U.P.U. must be the correct ones to ensure we stand together to bring the necessary challenges to this industry. Changes that elaborate the past but deliver a better future for all of us. Our operational mission is to uphold one world, one postal network. There is a determinant the universal postal union has been described as many things, a forum, a platform, a network and a community. But I want to add one more word to this test and outlaw with a concrete vision for this industry's success. For much of the 145 years the universal postal union has been a shared leader for the transformation and renewal throughout the industry. A voice of digitalization, e-commerce and financial services. And as we move forward with the future, I wish to inform you that we have formulated a roadmap that will keep this union in tune with the industry and general business tracks. Thanks to your contribution, we have developed U.P.U.'s postal vision 2030 that encapsulates the future of the union and the business of the industry. In this regard, we have identified four key areas that need to be addressed for the future development of the postal. The goal of the postal memory to encourage governments to increase funding in the postal development for their respective countries. Number two, throughout the integration, the new regulators are harmonizing their tools to enable the uptake of new services and the new platforms. Three, to add postal operators, address their performance and ensure that they compete heavily in the increasingly open market. And finally, but very important, is to seek integration of all players in the international postal sector. The vision has been tested, brought tested, and will hopefully form the Abidjan 2020 strategy and going on to catalyze this industry. But for real success, we must cooperate and we must coordinate and we must unite. Ladies and gentlemen, reaching consensus takes a genuine courage. Why? Because each of us must move away from our zone of comfort, and each of us must perhaps give up just a little of what we want. In the coming days, as you debate and discuss the subject of remuneration rates, I call all of you in the name of this historical union to find the courage to choose the right path, not just for yourselves, but for the entire industry. I thank you very much for your attention.


It's Ethan from CrankGameplays and today we are back in more of The Last of Us part 2 We in the last episode Abby got captured by the Scars. She was going to be hanged And then these two I think I think their name is Yara I don't know what their name is over there the one with the bow But they saved us Sort of for I don't really know why Because the one with the shaved head was like but she's a wolf And she said to cut her down anyway, so I don't really know why Why it was worth saving me Yeah Old you need supplies old world. What is old world?  Oh Baby, that's nice Does this say Eddie? I hope to God you're okay The latest truce has fallen apart and we've been ordered back home for reassignments I've said I've sent two search parties to look for you To no avail. Please send this note.  It's pretty sweet Spencer's getting into frisbees recently. It's very exciting But we're throwing that around, you know, having a grand old time having a grand old time Let's see Yes, yes, thank you. Thank you. Thank you. Okay, let's go back in here really quick and upgrade I Thank you. I just want to Double-check to make sure I didn't miss anything because I missed those Think we got it all. I think So we have 60. All right, so let's definitely dog We put a four-time scope on the revolver. Oh my god, well We're gonna do that because I think that this weapon is gonna be kind of hard to use anyway Little forex on our revolver. Hell.  How many do I have right now? It doesn't say I Think I maybe have like 10 or 15, but I think I think we're at the point now where we need 40 to 50 screws for any kind of upgrade but Just give me a just give me a whole big thing of them, you know, just a giant tub of screws.    Why not? All right I'm just going to I'd love to up the capacity on that that would be good Let's swap Hell, yeah, that's awesome That's so awesome Me likey. Oh, yeah, her arm is broken. They took a hammer to to that woman's arm. It's so insane So that's not very cool Not super great But also that means that she's probably not gonna be super helpful if If infected or other scars or anything come Or anymore that all of them Always stay in Loaded up just in case Get this guy melee style save me some mail feel kind of badass not gonna lie guys NGO Feeling a little bit badass, you know. Oh, yes, I think that just gave me more shotgun ammo and I like that. Yeah, I almost fell down there. Oh, no I fell out of the map. Oh, no. Oh, no, can I get back in? Oh, no. Oh No, I fell you fell out of the map. Oh, no, I Don't know if I'll be able to get back in I think I'll I Will probably need to I'll probably need to restart It's kind of funny though That was kind of funny though Coming through this door, right? They're not but they're gonna come in through there nice Nice nice nice now. We know is we know what lies beyond these walls. There's the world of gray That's pretty good though Pretty much the first glitch we've had in the game And I just kind of clipped through the wall And we're what? 15 16 hours in 20 hours in I don't even know how far in we are to be honest To be completely honest. I could probably probably check We are almost 14 hours in Almost 14 Just send one of them over Why would you send her over One keep her for collateral, but two like why send her over Why have her climb? Jesus Christ. I didn't know that you were right here, too. I didn't know I didn't know Jesus Come on. Oh my god.  They just abandoned me like that Well, that's what happens when you're not immune, I guess Am I gonna have to start that whole thing over? Oh, no, dude. I need to pay attention more.  They're so annoying. They're so damn annoying. I Know I can't I was about to say I should make some other bombs, but Don't have any other bombs to make.  Oh Dude, you almost got bit by a clicker. That was really really really close. Oh Jesus Jesus Let's go Yeah, yeah, yeah, yeah, I probably hurts on your breathing quite a bit We can't walk that fast And out oh I hope that you can protect us Can I put her down? This is gonna be one of those oh gosh, this is as fast as I can move right now to Plus there's one to the charm Faster go faster Perfect. There's a couch God Just a warning we gotta we gotta set the bone back in so Jesus cry. Oh, no. Oh, no. Oh, no. Oh, no Oh, no. Oh, no. Oh, no. Oh, no. Oh, no. Oh, no. Oh, no. Oh, no Not he died. Why do you do this?   Oh, we just peace in yeah These are all yeah, those are all locked at no point No point Let me just get to the aquarium game, please Please just let me get there without so much of a ruckus. This game is so brutal It is so brutal. Wait, hold on. I don't want to do this yet. I want to just check around first see if I find any screws Give me that health. Oh, I love those little bars. I Love the way that they give me Nutrition and health Makes me happy. I don't know why I didn't have my light on start to sell Dorkies fuel Fuel. Oh, I wonder if I'll ever see them again Or if they just save me and that's it. Yay Yeah, yeah, yeah, yeah, yeah, I want this yay equip Equip now we have holster thingy That is nice Holster thingy and that is nice. All right, so now let's go back See if we've got any 49 okay How much is it to max out the shotgun 60 Man, there's probably a couple fifties in here, too, and I just need one more Might be might be able to do one in here you fire rate Man the capacity would have been nice Well, let's just Let's just save it Just save it for the next one And we'll have have a good amount of stuff Okay Time to peace on out Fucking knew it. I was about to say there's way too much cover around here. It's just infected, right? Think so What kind is the is the issue come here Come here. Thank you for the paper. We got clicky boy It's the one. I think it's just the one I'm over here. Okay Okay needed a shiv.   I can do this.  Can I make ammo yet? Okay, at least I can make a shiv Make a shiv and get rid of it that way.   Okay, we still got it.  Ah that away That away Gamely give me anything. No, not a coin. Alabama Coins and what I want, but maybe it's what I need. It's not what I need. I need ammo Med kids should be a straight shot. It's not going to though. You know that. Yep Good timing. Oh Fantastic timing. That's great All right, let's keep keep on kicking Let's just keep on moving long Oh This is not going to be good You prepare to do some swimming? All right, see if we swim underwater Then we won't be affected by the big big waves, you know, there we go easy peasy I haven't swam in the ocean in a long time In a long time.  I think she's pretty shaken up by the violence of it all She asked mommy. Why did daddy push all those people? I told her that it was the only way for us to get aboard She nodded, but I don't think she fully comprehended maybe I should have said something different, but I don't know anyways if she wakes me up if she wakes up before me Read some of her books with her that seems to come her down. Hopefully you were able to get there The ration station sorted out. Love you coin It's sad. Yeah It's fucked. Well got a bunch of arrows now. We just need a bow, huh? Now we just need a bow crossbow Oh, yeah, dog digging it. I'm digging it. I like it me likey me likey I like the crossbow so much. Oh There's no like drop-off really either God, that's so nice still need things to a And the like the likelihood of a headshot is probably a lot higher, right? Oh They probably don't have that just because of the force of the crossbow. Oh I guess they do with some or they're sturdy and can be recovered more frequently. Okay Thank you for your help with that infected passenger We're lucky to have someone with your training grid at board where our crewmates are useless And I don't agree with the captain keeping the weapons locked away We can't stay willfully ignorant and have infected passengers on board this ferry The weapon storage is on the top aft top deck combos 90 77 1 Crossbows in there. I trust you on this 90 77 1 God, I wish I had any kind of health Me so running real low There's a couple over there Damn it. I waited too long Anybody else? Thank you. Thank you Still not enough stuff West Virginia mountain mama Yes, we got the mountain mama coin guys Great news. This is great news. Just want to make sure I don't miss anything over here. Oh Medkit. Oh, thank you. Oh, thank you so much.  I love the crossbow. This is like my favorite weapon so far So perfect We're stealthy manavis. Just want to make sure Nobody else is around here is This safe so damn good Booze. Get some of these back Get out. Get out. Get out. Get out. Get out. Get out. Get out. Get out. Fuck. I'm gonna die That's my death. You just do that more stealthy. This guy Bye bye guy Then We'll get this guy. I Think I remember it 977 and then One There we go Ooh urban warrior Wow Fun fun fun close quarters All right, let's just see really quick 117 that's good Cindiary shells this pretty dope. Hell yeah, the cindy area bullets is so sweet. I'm gonna save it I'll wait until he walks back Because I can easily get him.   What's she right? Interested Interested I am I Don't know anything about sea knowledge Utah Let's just reload everything much as we can soup or quick. Oh wait I can craft ammo. Oh, yeah, dude Hell yeah You'll love to see it Let's uh Cool excited for the the incendiary ammo. Oh, I wouldn't need to go on top of that Worried about scars being up here worried about everything all the time mostly to be honest To me Christ, I don't speak here. I Don't know why I don't know why I'm doing an Irish accent. I'm itching my ear. I'm vulnerable Please don't attack me while I'm doing so all I want to do is make it to the aquarium, dude All I want to do is make it to the aquarium We're so close to being there, too So so close and we're basically there Just gotta Figure out the puzzle The way to get through thought they would have put something there. I guess not There's gonna be scars down here. Do not trust this area at all Gonna be honest Do not trust it. Here we are Back how we get there Still wondering how Mel got all the way down here. I mean Theoretically, there shouldn't be infected around here, right? Because he he cleared this whole place out theoretically of course I mean, obviously we'll need that but I'm just not really sure for what yet. This is probably locked. Oh wait. I see now.    Maybe not maybe out that way this is easier There you go.  I mean to be fair I wouldn't I Wouldn't blame him if he played if he got mad at you for the glass cuz dude How hard is it to replace glass in the apocalypse? Streamly is out here. I hope they didn't her Allison She a good dog. Hey, are you listening to cold play? It's not a cold play. Oh I thought that was him for a second.  What happened He's probably in his room thing Well, wait, maybe he's in his boat actually I think about it I was thinking that he was gonna be in the big like see room thing. What are you doing, dude? He didn't make her part fix her back up. Oh I see There's a gross hooch that you had made Danny's dead. You want to tell me what happened and out of the small camp? It's just a couple scars and Goes down and his weapons right there and he doesn't go for it.  I can fix this. I'll talk to Isaac. I'm tired. Have he I Don't want to fight over land that I don't give up. I'm going to Santa Barbara. It's a chaser rumor Santa Barbara's where the fireflies are Grouping They're gone. Of course. We know he doesn't end up saying it through. Oh, yeah, what about Mal dude? She's pregnant. You cannot just abandon your pregnant girlfriend.   Sorry I grew up You should try it. Oh, yeah, how do I do that? Try to find the people that killed my family Cut into them torture them till they're crying Bad Being on your girlfriend, dude I like I get where Owen's coming from with with just being tired and just like He wants to go and try and find the fire the fireflies because he has hope And he wants to like believe in something again. Oh, is she dreaming? God, I went back.  He looks like a Chris Seattle day two This is the present.   Did she just like track them or something? Oh, I'm just backtracking right now Yeah, that's the It's the thing Hello. Hello.  I wonder if we can even get the the like big dude with The crossbow there's a lot of them God damn it. Hey, you can get him. Fuck. This is not Not at all what I want credit games guys credit games I'm going to switch from this That What? How did it work the first time? Sorry, I Do like the They shut them that is good idea Can I I cannot? Maybe I can Snipe a few of them. There's definitely more. Yep. Hi. Damn it.  Yeah, haha Yeah, yeah, yeah everybody That would be super nice That would be super nice if it was everybody Because I don't have much health You know don't have much health Let's see that's only three at the max and it's only two right now. Okay Okay Cannot craft any medkits yet That wasn't really that hard. Actually, I don't know why I had such a hard time with it I think I was just rushing. I rushing or am I dragging? I don't think there's anything in these Probably just go through the top, right?  Yeah, well none anything before while they're briefings now after especially after I've already looted this whole place Well, you know, let's just see if there's Any upgrades that I can do I don't know how much stuff I've got Yeah, 88 before it's scope for this Reload speed might be really nice for that actually. Let's Think about it Let's see real. Let's be that would be good. That's that, huh? That is so cool That is so cool Still where where are they? Oh, that's right. How do I? kid You're still there. It's me. Oh Scatios.    I Had a very minor. I've only broken a bone once I broke this bone in my hand And even that just like I remember the day after I broke it I didn't know it was broken yet And I just had it like wrapped up And someone noticed me out in public and they shook my hand and I I like held it in While while it was happening, but as soon as they left I just started crying Like I just had like tear. I was trying not to cry so hard and as soon as they turned around I just had tears flowing down my face.  Why won't she put? Sure is broken That's the surgery thing.    We leave it. It'll turn gangrenous. Oh, what do you need? Ideally a Saw sutures clamps antibiotics. We're far from ideal right now We have knives fire cut cauterize it She would die from infection Make me a list. I'll go to the hospital. I'll take you all day to get there. I don't mind It's not about you. Abby. She doesn't have a couple of what if I can get you there in two hours The Wolf Hospital, right? on the west side Wow, we built bridges Hi, it's how we get around the flooding and You people you people can't handle two hours. So make a list Wait, are you serious? These bridges are used by scars. They only send in small groups at a time. You heard that small groups Why wouldn't they just send? Her that scar I still don't know her. Oh Lev. Why wouldn't they just send Lev? Like that it doesn't make sense for Abby to go it really doesn't unless does every scar know that they're What? But they've sort of like turned against them or whatever my keys Sorry, I don't care about last night. All right, Lev. Let's uh, let's go Let's rock She's one of the best surgeons in Seattle Owen oh We get to the really tall buildings the bridges there How the head kicks out toward downtown? Wonder how young she is at the edge of the Russian water You get us there and I can take over These bridges are really gonna get us over the rapids. Yeah, all of them. Yes In just a couple hours. I mean, why would she lie about it? I'm coming Abby. You don't have to come in wolf Okay, I see it I Mean why would She'd probably die keep out of the water these rapids will rip you away. I know You know how to swim, right? Little puzzle of the rocks You've been to these sky bridges before right?   I'll do whatever you want. I'll come. I'll cut my face.  I don't want to die here. Please help. Please help. They're gonna find me They're gonna root me apart. Oh my god Like so afraid of infected It makes sense Makes sense.  We live in 302 didn't know anyone else is still here. We're not scary We swear Leaving behind a freshly baked treat. Thanks for the cornbread my mom told me to give you this bottle of vodka I hope it's a good kind. Why don't you guys get on the bus with everyone else? My name is Julia. My mom's name is Haiti or Heidi. Where did you find this vodka? This is legit.  We'd rather take our chances here. Let us know if you or your mom need anything Thanks again, gonna look for more cornbread mix while I'm out That was a game changer. What if you guys to help offer with my mom?  Just knock Scar saw James cooking on the roof. They shot him.  I want to go downstairs first. I think that's probably the way out up up there Never mind can't do that Wait, there might be a way into one of these other apartments Unless it's a different apartment, but I don't oh here we go three It would be three. Oh Oh three and three oh two wait What is what is this apartment number just realized this is 302 What is their apartment number our wood? Combos our apartment are our apartment number than your apartment number So it's 302 wait. This is Sam, right? Yeah, so it's 302 and then Okay, let's try this again Three oh Maybe three oh three.  There we go.  Let's get out of here.    Hey get off of me. I swear to God. Oh Yeah, yeah It's gonna go big explode so watch out and We let the air dissipate and Now I think we're good any more use Yes, a lot Many wolves have you killed? Shotgun ammo Me like the shotgun ammo, okay Okay We're now Where we go now? Hmm up there.  I'm still going the right way Yes Wait for it.  I meant to do something else. I'm so sorry. Don't worry about it I need to be really careful I've done stuff. What if we do this? Come on. Yes Yes Yes See My way might be a little better. I think I'll probably have to go back There might be stuff in here cool stuff stuff we can use There also might be no stuff There literally might be close to nothing in here seems like there's close to nothing in here, so This trip might have been worthless Yeah, oh you're here. I'll take us to the building next door Okay, cool.  There's a way around if you don't want to know I don't want to There's a way around is there Well parkour Not afraid of heights Wait, she is afraid of heights actually vertigo Well, I'm technically afraid of heights She just has a vertigo where like if you look down at big heights is like Assuming Abby's not gonna do that Actually isn't that hard Abby pass along the elders have agreed to a truce with the wolves They will stay away from our island and won't engage with us with any sufferites passing through their Outer territories to maintain peace we must all work together our goals remain the same These are simply different means to achieve them who broke the truce first I might have already said that actually this way Wolves never look up What does that mean?  Come on. Can't do that. That's that was mean. That was mean. That was really not cool Got e Hello Sometimes I do really good Sometimes I really really don't there we go You okay that everybody? I don't have any more elbows No, no, I got it. What'd you do? Did you hear what they called me? Apostle. Yeah So she's the one that you killed Scars built all this Yeah, I was gonna say that It's pretty cool What's cool? like impressive awesome I wonder if your prophet had any idea what she was starting She saved dozens of people In ways no one can explain She blew up trucks and killed some soldiers not that hard to explain Have you read her writings? Interesting, that's cool Sure, I don't have enough It's interesting. I like how they changed that for the Sephirates. I'll go first this time I Was thinking that maybe you would get the second one, but okay, but okay, sure.  I'm sorry. All right. I'm sorry. Sorry. I have all this stuff I want to just get a clean headshot. I don't know why the these headshots aren't working as well as they were before Thank you Bless you. Thank you. I see I see I see I love you're really not helping out that much You didn't see anything. Where did she go? How fair are you at? Whoops.  Why didn't it are there any this way? No anymore. It's craft a little bit ammo. Is that everybody? Where are you, dude? Oh oops, I Was pressing the wrong button come on Why you do that dude Not cool. Just come out Just come out Keep out say hello Say hello to us your friends I'm gonna say hello for you. I think that's everybody So Seraphites, whatever Yeah Never heard a seraphite cuss before Oh, it's cute. Well keep going up. Yeah, man. I've got nothing Gee whiz I do not have anything swap this. Oh never mind. I do have 14 That ammo that is nice could use that For melee weapon Just kidding. We can do you this for me. They went into you Just keep going up up and up and up and up and up. I need scissors Seizures Just keep going up and up and up So you can't go up no more That's the that's the whole deal So y'all have oral lamp, but you use an elevator.  You're more focused You don't feel pain as much That is true Every bad feeling Your palms sweating, your heart racing They're all signs you're actually strong You've my hand sweat so much when I game and that's just a sign that I'm growing stronger Very interesting Yeah, I thought your anti-electricity and all that simple old-world stuff There are exceptions especially for soldiers That's convenient Not a lot of loot around here.  You're lying It's yeah, I can see why it's not the most popular route Jeez.  What's to be impressed about? What's to be impressed? She does it all the time.  Let's win two three guys on me He Like if she's done it I've never really had a problem with lights Like I think it's that I would be able to do this It would be the thing about this that would be sketchy is not necessarily the height It's the Wind that I'd be afraid of like being blown off This is pretty wide. It's not like a beam or anything. Oh good. Abby. You got it Okay, now this this part is pretty sketchy This part Also pretty sketchy She's gonna fall We can never get anywhere Properly can we we're so lucky that that's where we fell Dear God, we are lucky. What do you think about in those like that like second that you're dropping of like Even think about anything Like I think a shower. This is the right building Let's see if we can find our own way down scrumptious that's the worst of it and we got off lucky Maybe it wasn't luck Maybe it was Some wolves believe in God. I've heard them pray Yeah, I mean you're right. Well, I don't if I'm gonna die.  Guilt of what? You don't know us anything. I just Needed to let him load a bit. It was safe me like the safe Me always like the safe All right, what we're looking for is a piece of paper left About yay big all right. We've got to find it We get that and We'll save the world But I believe that Aang can save the world Ooh, but there's something in here. I was thinking more of a Piece of paper with a note on it with a With a with a code whatever Whatever nothing Why you got nothing back here. Come on Wait, here we go Please don't leave valuables lying around while you're on shift We have an employee safe in the cleaning closet in the lobby because code is the same as the Wi-Fi Okay, so now we have to find the Wi-Fi code. The Wi-Fi code is probably posted somewhere, right? Like publicly, I mean because other people in the hotel are probably using the Wi-Fi Maybe maybe not Hmm Hi, Steve. We could I have Wi-Fi code? I have Wi-Fi code What Wi-Fi? Wi-Fi code. Let's see Nothing there. What is the Wi-Fi? What is the Wi-Fi?  The wolves at the hospital? It was wolves at the hospital Don't I have yours? No, check out the clothes Here Looks dark down there. I see how this works.  Do you guys not believe in gas masks? We were on the run Stay here.  I'll be stuck here.  Oh, yes Shot gun ammo Do-do-do and load it up, please all the ammo you got Anything I ammo. Oh, man the spores are Scarier when they actually affect you. I think that was a I think that was a big boy. I Craft more of these now. I can't craft a lot in general craft one more of these Just in case Any gas mask in here? Bugaboo bugaboo Creek Steakhouse I don't go in there, dude I'm gonna That's a little bad. I miss having a friend Yes, gas mask wash that out at all or it's gonna kind of leave it Looks good.


I'm very bullish about it. All I can say is that I'm very bullish both about India and RR's capabilities and I should say RR's initiatives because it takes two to tango. And I think us as a company, the UK as a government and India as a government and the three coming together brings the capabilities for us to do more here in India. And I think the stars are lining up. So I think it's a good sign. And it's expected to easily go up to four. So I see the sector is still in the early stages. I see there's a lot more happening. It's going to be more of international travel. And more importantly after COVID times, people are attracting. And today I was observing that all the airlines are filled, all the trains are filled. It seems like people don't want to stay in their houses anymore. They really have wheels in their feet and they want to go somewhere all the time. So this is tourism. This is business. This is just casual. Anything you look at it, people are traveling. That's the first thing. When people travel, they want to get there faster. That's the next thing. So aviation is here to stay. Well, RR has been in India since 1932 with that part of the main actor. Then we were the Indian Air Force, Indian Navy, 1956 our partnership happened with the JL. So when you look at our journey, we have sold engines. We have partnered in India. And then as we went along, we built our engineering services around 2005. And then we have not looked back since then. We looked at the operations side and we leverage the capacities in India. Then understood the capabilities that existed in India and started building out of them. So making India was the best opportunity of time. Now, when you're going to just buy from overseas, it is one thing. But if you are able to buy these large defense projects and you're able to make them in India, then what happens? You in principle have not just created employment. You create the security of sorts for your defense equipment. And now you translate that into the other areas, pharma, food beverage. And then you keep looking at it, manufacturing becomes a very large portion of the economy. It gives security in all different areas. And at the end of the day, it was an initiative, a vision, a clarion call by the Prime Minister. We have evolved since then because you have said, yes, making India is great for us, but we need to do more in India, which is where you're at. To be honest, I think the Air India deal was a significant deal because it's a significant milestone. And I think with the 1932 Tata Bay for us to come to this Air India deal here, it's a full circle. It's almost coming home. And it's with the white body aircraft, the Evers 350-1000 and the 350-900, which are really beautiful products. And by beauty, it's not from an artistic sense, but in terms of technology as well. They're cutting-edge technology. In fact, our engines with Air India, they will be 50% SAF compatible from Lewa. So not only are these engines, just engines, carrying people from point A to point B, they carry them much more clearly. Of course, COVID, I think everybody has had challenges with supply chain, which is a global challenge. And we continue to work with the global challenge, and we look at how India participate with us in those efforts. And for us, whether it has been a supply chain challenge or not, the way to look at India is a very long-term proposition. India is not something you come in when you've got a challenge elsewhere in the world. I like to look and say, Rolls-Royce has looked at India and said, India is my partner for the rest of my life. We have had this relationship with HAL since 1956. And when we do something in India, it's always been a very, very long term. Our adoring engines, you know, power the combat aircraft in India, and they've been going on for the last 30 years, and they'll continue on for a sizable time to come in the future. So these products are very hard to design, but once designed, they go for a very long time. And so with our partner HAL, we're able to support Air Force. So in my view, I don't want to look at it and say, oh, there's a crisis in the world, so I think you are going to call it India. We look and say, India's got these capabilities, India's got these capacities, and we are here to leverage India for India and leverage India for the globe. A couple of things to my question. We signed up to the NetZero chart of the UN by 2015. So we signed up to NetZero, which means all our facilities, all our products, all our services will be in NetZero by 2014. But it's a journey. But no journey there that we can sign up to something, but if you're not showing along the way what you're doing with it, it means nothing. So what you've done with that is we've recorded and said, our existing products, right? And our new products. How are we going to handle that? And in terms of the new products, we have said by 2013, everything will be all the NetZero, or a safe compatible 100%. The regulation today says 50% compatibility is enough, we've got 100% of our capability there, right? But 50% we'll be able to do. And now with the existing products, we're going in there and saying that now we've got to retrofit all of them so that they are also 50% SAF and antiviral regulation. And when you go to 50%, you can also test in those sort of ways. So we'll do that. And that for us already there in the campaign that we have had, I think in there, in principle, all the agents are there, right now they're in here, or 50% SAF compatible. So from day one we're able to achieve that. Our facilities now. Now we have to look at the facilities, we have to look at the services. When you say NetZero by 2050, it's got to be everything. Those things we are saying, we'll work towards getting them ready by 2030. So this is one side of the picture when there's more of an evolution. Then you go to the revolution side, right? The destructive side, which is like, I'll eliminate all of these fossil fuels, you know, powered aircraft, and I'll go all electric. So now when you're going all electric, then you start looking at things like green hydrogen because if you say all electric and the batteries are charged using coal for power generation, it means nothing. So we basically said, you can look at green hydrogen, you got to look at how the batteries are going to work, we got to look at how this aircraft will fly. So we created an aircraft and we said, let's do a test run, let's do a prototype, and let's check it out. And so that aircraft in the first trial was a success. And now we are able to say that, okay, now we take it up and we've got to go longer distances, we've got to go faster, we've got to put more payload into it. So all these things start coming up. But that's a different journey altogether. So you've got two efforts. One is minimize the carbon emissions, okay, or control it as much as you can. The other is eliminate those in a different way. So there are two paths you take. Then you have the electrical, you know, the EV tools, electric vertical takeoff and landing. Now these are like for smaller, so there's a transport system that's evolving where you can have like five passenger helicopters that in principle can act as air caps. And so the air taxi service, if it comes up, we have our EV tools that we are working in many companies slowly. And so that's again, that's going to be a much faster entry. But then this is airspace. This is a very different kind of regulatory environment. So we have to work with a lot of people in the government, the academia, the industry, and make sure these all become products for commissioners. So the journey is all for us. But it's a long journey. It's a long journey. It's a different journey, but it is going to be there.  It is not how important this, you know, India for our art. It is also the question of how important it is, how important it is. From an India point of view, we are a team that supports our local businesses. We make sure that we are there alongside them in creating new products or new technologies. We are with them in analyzing the data, in creating the tools that are required to make sure that the existing products and the existing fleet flies safely, reliably, and efficiently on the aerospace side, and perform safely, reliably, and efficiently on the power generation side. Right? So in principle, we have an engineering team supporting all the three businesses. We have digital teams supporting all the three businesses. We have a joint venture here exporting products for global usage, and we are providing the local employment and leveraging the local capabilities. So it is a very integral part. And it is not a question of what is the percentage of this or that. It is a question of how integral you are and how important you are. And that I can say we are very important and we are very important. And then our force motor joint venture, which because of COVID times, we struggled to bring it out. Now it is all performing. We actually make about 1000 engines a year there. So I think that is also more forward. Joint venture is doing very well. Digital team is doing very well. Now engineering teams, we have about 2,500 people through our partners TCS, L&T, you know, and others, Infosys. And so we are able to continue to provide that support. From a support execution point of view with the Air Force, we make sure our engines are flying without getting permanent. And we make sure that with the Navy, with the Army, our products are supported. So there's a lot of areas that are our technology here. There are a lot of products and services that are our workforce that India can leverage. And I think that is what we would like to do as we go forward. Hand in hand.