 So I get started right so today we're going to be talking about building a restful API with Scala Z. So how many of you know what Scala Z is one. All right, so so I'm Yashun Kumar platform engineer make them systems. So we are a startup. We are a cloud startup from Chennai and so we are like such a past platform where you could launch applications. Services and you bind them together something like Heroku, but we also do the monitor them and you have countries integration all this stuff right. So the agenda is pretty simple. So we will look into Scala Z library quick intro and Scala Z library and then like what it is and how to use it and then rest API the gateway architecture of the API server. Okay, so this API server. So say R is a cloud platform. So we have an API and API server that takes that does the full heavy lifting there. Okay, so it's a loosely coupled architecture. So we have this API which does pretty much everything from the rails on top. We have this API and it's connected to a message broker and then a pass engine and stuff. So this does pretty much all the work. So we got so that is written with Scala play and we've used Scala Z library to work with. And yeah, so I'll also show you some real time use case Scala Z like basically the code of how we wrote it and stuff. So why functional? Okay. So why functional? Right. So we know software is getting complex as in as gets really complex. You know, you want the software to be well structured. Right. So and then well, we all know that immutability. So we all know that there are no assignment statements in when you're writing functional code. Right. So you don't. So it's immutable. Right. And fine side effects. So we all know functional programming is all about not having any side effects. So what do you mean by side effects? So say, say there's a function. Okay. It takes in a type A. It gives a result B. That's it. Right. So it doesn't do anything else. It's not straight straightforward. It takes a type A type B. That's it. So in. So what happens is that you won't have any side effects. Okay. And there are no order of execution. So it's irrelevant. I mean, you could do which order you want. So basically that particular function is going to do one thing. Right. That's it. It's pretty elementary stuff. I mean, anyway, so pure functions, you all know what pure functions is. Right. Something that has no.