 I'm going to talk about someone else's service. That's a topic which I am going to explain later. So, I'm Chathu Ishwajit. I'm from Sri Lanka and I'm also your ambassador. You can find me this handle almost everywhere except Instagram. So, serverless. I'm going to explain you what is actually serverless. When I say serverless, it's like this. You're saying it's no service? So, yeah, is that all zero that the company is running without service? No. So, let's talk about what is serverless computing. The word is actually about serverless computing, not the serverless just a word. It's like a buzzword used to get some people going on. So, if you are going with the quick history, how it happened? So, it is like companies started to own their own servers. So, they started creating jobs for network engineers, load balancing and everything else was there. And so, they run their own physical servers, which is a kind of really messed, even come to patches and maintaining these servers. So, it's need additional stuff rather than your main business goal. You may be creating your own application, but you need to create, have another set of stuff just to maintain the servers. So, then people started to give their own idle servers as a cloud and charge it for about how are the bases? So, yeah, it cuts the bill about considerable amount and the maintenance costs also get less down and you can actually have less number of stuff to run it. You need to set up the servers, which is you need to know about DevOps. I hate DevOps, yeah, that. But you need to know that if you are running on cloud, you need to know about how to set up the server, how to set up the base image, install the dependencies, maintaining it, scale it, everything, yeah, sort of hard. So, then a company schemes that we can do DevOps for you. So, they call as platform as a service. So, like Heroku and many other things you may know, even from AWS itself, there's a platform as a service from there, like Winstack, Winstop. So, companies evolve to the past, but still not enough. So, the rest of the people come with software as a service then. So, we will give the mailing service as a service. We are giving semis or messaging service as a service. So, you don't need to set up your servers or your application, you just use our API and we are going to charge a little bit for it. So, new business is going on. Then, people came, why don't we give a server as a service? So, we set up everything. This is part structure and everything. You just need to put your code and we do the magic for you. So, this concept has a buzzword called serverless. Some people call it cloud functions. Some people call it as microservices. Some people call it as a function as a service. So, whatever you say, actually, it's just a server and it has everything that required for your use case pre-setups. And another thing is actually it auto scales, support auto scaling and you don't need to pay for your ideal cost. So, if your application is not much used in nighttime or some time phases, where in normal cloud cases, you just keep your servers running on. But when it comes to serverless, it only charge for the request. Just fire it up and do the task. And for the amount of time that took for the task, they only charge for that one. So, that is actually serverless. It's still someone who is a serverless. Only thing is you need not to pay the ideal cost plus your support auto scaling. So, whatever number of requests you are coming, the server will be scaling and do the tasks for you. And you don't need to learn about DevOps. You don't need to maintain the servers. You don't need to check about updates, patches. Yeah, everything is going on. So, what are the examples of these platforms? Support is this one. So, adepts to use lambda, which was the earliest in this game. It was called earlier as Jaws, later it became the lambda. And Cloud Function from Google. It has Google Cloud Function, plus it has Cloud Function from Firebase. So, yeah, they joined the bandwagon. And Azure from Microsoft, they have their own functions. So, they also joined us this one. And the last time, the web task, IO from OZO joined. So, you may think that if I am going to write an application in these things, it's like you are depending on these platforms. But there's an open source project called serverlot.js, where you can use it and make it the provider with the ratings. Then you can actually run your serverless function in it. Almost this, all four services. So, if you are going to start with web tasks, IO, you just need to NPM install the WTCLR, just globally. Next command will be about anything. So, you just WTNP with your email ID. Going to give a account just from the command line, sign up in there. And this is just the hello work. You just export the module with the callback function and just echo into the normal file. And for running, you just type create. WT create with your application. That's fine. This is really painful. No, no, this is not that hard. So, there's another way. If you're not like a fan like me in command line, there's a web editor you just type WT edit. It's going to give you this URL, which is going to look like this. This is the editor. So, let's get some demos, zoomable. I hope you can all read it, right? So, this is the basic editor from WebTask with IO. It's suppose not 8.0, and you can just type your normal JavaScript in here, and you can serve it in, like in here, just an endpoint. So, I have a small application, which uses its own WebTask or your storage. You can store JSON content. If I run this, let's see, first run this, and then I can explain it. So, it gives a tip. It says, so-called as cross-effective. So, if I want to put another data in here, I just get post request. So, it says saved, which is from this part of the code. So, if I see a cane with a get request, you can go to direct to this site. So, it says add all the tips that I've posted already. Let's get into a little bit easier example than this one to explain. So, this is the normal hello world that I explained it. So, it has about function, a normal function with a callback. So, you just send whatever the thing that you need to output in here, or you can go a little bit more like running a total express server in the endpoint, and you can even write your own mail gun to just send an email. So, many possibilities are there. Even you can run stripe payment. So, if I go to this URL, you can just have endpoint to spell. So, this is my API, I guess. So, if I play it, it's going to give my... Anyway, it's going to open it in test mode. So, it's going to be like that. So, every endpoint is just an JavaScript endpoint. You can put whatever you like, express, or whatever you normally write in Node.js. You can put it, and all the dependencies also you can installable from here. You just go to there. You can see the old NPM dependencies, and you can actually install whatever you... the most other dependencies you want in the project. If I move to the presentation again, these are the limitations currently with the webcast.io. Is it free? Yes, it's free. There's a soft limit of one request per second, but it's just a soft request. I tried more than that. So, it's working. And 30 seconds of execution limit, and you can set up trend corner of schedules, which I'm going to explain what is actually this part, the ground schedules. And for every code file, it has a limit of 100 kb of... for task. And 400 kb of the JSON storage, if you are going to use it, you can use it in normal MongoDB or whatever you do. And for resources, you can go to webcast.io.slash.docs. Let's get into the webcast cron. What is this webcast cron? So, webcast cron is actually a... it's a normal kind of a Linux crontet, but your serverless endpoint will be called these given times that you set up. So, you can set up a time period that you want, like in here, in scheduler, or you can use it in the comma line also from the WTCLI. You can schedule an endpoint to call on a given time, in a given time zone, just like a crontet. So, every time the setup will be fired from here, or you can actually have kind of hooks, like from stripe, a hook, from to call and webcast endpoint. So, these kind of things are possible from here, and that's all for my presentation, and let's move to the questions. I hope my time is going well. You are well ahead. Right. Let's go. This is my phone inside. Just talk with it like this. Okay. So, one question. What I haven't quite understood with the serverless is what about state? I saw you were saving something, so the storage is separate from these functions in some way, so the storage will remain until your next function. Yeah. Storage actually, in webcast, your storage is actually a destination storage, which is a persistible storage, apart from the idle time. Okay. So, it is only endpoint, then it is only going to charge for the endpoint call, but not for the storage actually. In here, it is actually free, totally free. Anybody else? And you can actually connect your MongoDB or normal database back in there, and only when you call, it is quite updated in the database. Still there. Others? Thank you very much. Thank you very much for welcoming us in here.