From Servers to Serverless - Guillermo Rauch - @ServerlessMIL

[Music] [Applause] how's it going figuring out the screens right now there you go thank you thank you for all of you who've stayed behind for the last definition of serverless for today it's true so a little bit

about me first I'm the CEO and co-founder of site builders of a lot of awesome dev tools our platform for service is called now you can go to it now that it's aged and a fun fact about me and from Argentina so this talk is not gonna be in English it's gonna be in loon farther which is a variant of Argentinian Spanish mixed with Italian for the purpose of dancing tango I don't know it's a lien but I think that's what

it says there cool actually I like he said I'll at and now live in San Francisco so the talk is gonna be in English okay so one term that I want to introduce that I haven't heard of today that I think it's really insightful is server full because we toggle a server so into our server less and feel like it's not symmetrical enough so this talk is actually about talking about server full to server less so let's get this last definition out of the way so what are the questions that

come up in my mind it's served as a cost model is it a security model is it a programming model can a container be server less CC bread and cloud run it several as a religion that's a good one I actually I'm thinking that it is based on some of the dogs I've heard can a server be server less this one is why I spend a lot of time thinking about can a server be serverless because we see that

a lot and this is my reaction can its server be serverless okay so my principle about this is that opinions are like butts and everyone has one Socrates not really definitions servers are like butts every platform has one so depending on who you talk to like me who has a platform we'll give you a different definition but since it's the last ago today this is the one definition that you have to hold on to

so my definition is actually quite novel I think I haven't heard it today so it's very simple if you deploy and operate a scheduler your server fall if you deploy code that gets scheduled by something else your server less so it's that simple kubernetes server fall it's literally a distributed process scheduler containers this won't throw

you off server fall why because inside the process you typically have to deal with a scheduler functions serverless because they're invoked by the platform that's why we talk about invocations when we talk about server less or a lot of us do this one is the one that throws you for a loop servers inside functions like if you take Express rjs or a node HTV server you put them inside function serverless why because you're still

being invoked by the platform whether you're writing server code perhaps fights off the abstraction a little bit but because it can't be made at work I'll give it a server list with an asterisk and some of the caveats have to do with for example granularity which I'll talk about later and making some sacrifices of the security model that you get from server list when you deploy a server with multiple routes inside and then there's the discussion always of