[rhlsthrm]

I think of it as "zero ops" API endpoints. I have some serverless functions deployed on Vercel. I wrote some Typescript code, pushed it to a file in a directory called api/. Now every time I call my function endpoint, the function runs and returns my result. I don't have to provision anything or set up any ops. The serverless part takes care of spinning up whatever compute it needs, runs my code fully statelessly, and returns my result. I don't have to touch or think about scaling anything. I'm a developer who wants to spend time on features and code, and remove myself from the dev ops as much as possible. That's why I love serverless and use it whenever I can.

[toshk]

Thanks, still curious about data management, vendor lock in, what to do when complexity grows etc. Im sure they have all been thought off, will look into it.

[jjice]

As for vendor lock in, I think that is one of the bigger constraints with serverless. There are a couple tools that help make the transition easier, like Serverless Framework[0], but when you get into things like AWS Dynamo DB, which seems to be there perfered DB for serverless workloads, it can get tricky. Thankfully, it seems like the format of basic serverless functions is pretty standard across different platforms, but I think the real tricky part comes from other services on the platform you use, like data persistence.

[0] https://www.serverless.com/

[pavlov]

Narrator voice: “It had not all been thought of.”