Alt text:
be me
serverless supervisor
in charge of making sure the serverless environment is in fact, serverless
occasionally have to check if it’s really serverless
one day, find out there are actual servers being used
serverless environment is no longer serverless
distress.jpg
ask my boss what to do
he says “just make it serverless again”
I say “how”
he says “I don’t know, you’re the supervisor”
rage.jpg
quit my job
become a servers supervisor
first day on the job, go to the new server room
it’s empty, serverless
Fucking servers, how do they work
Maybe, like magnets?
They work better if you don’t fuck them.
Did this come from a series of AI generated green text? I seem to remember the story.
It was originally about bottomless pits iirc (and yeah, the poster claimed an AI wrote it)
That’s exactly what i remember yeah.
I actually think this version flows better
idk, I stole it from a Telegram channel.
Appreciate the honesty!
Yeah, but it was a bottomless pit in the original.
Does serverless mean, you’re hosting on someone else’s servers?
Serverless usually means that the servers are ‘hidden’ from the user. You only get one shell, one desktop environment, but on the backend, your session might be split between multiple servers. Or it might not be. You, as the user, won’t know. It is basically an abstraction layer between you and the servers themselves.
To add, it is typically manifested as generic ‘compute’ or in the case of azure ‘functions’ where you environment the code is running on is abstracted away, instead you are just paying for compute, e.g. this function takes x time/cycles to run and so it costs y to run it each time.
In theory you don’t need to worry about scale or anything, just deploy your function, and pay for what it uses.
Surely this will never come back to bite me
Yeah better get really good at paying unexpectedly high invoices. Or if you want to know ahead of time what your costs will be, hire three specialists who will monitor your not servers as their full time job and make sure your „functions“ are not bankrupting you in a month. If you think you sleep too well, go serverless you’ll never sleep well again.
One Riker, one bridge!
Serverless means you don’t have a server running 24/7 that’s sitting idle waiting for requests. When a user makes a request on a webpage/app it’ll run a short lived piece of code for a few dozen milliseconds then shuts off. No permanent “server” running. Of course there’s servers running the code to start that function and usually a permanent database server but the main app/website code is running on demand only.
Sounds like the same result with extra steps?
There’s a few advantages. No server maintenance is one, but the main benefits are scalability and cost. Renting a server is expensive and is billed regardless of usage per month. Serverless is billed in 10 millisecond blocks so you only pay for each request essentially. Since it creates one compute function per request, it will more easily scale up to meet a surge of users. Of course with any trendy technology it can be misused to situations where it’s not a good fit and lose the cost and scalability benefits.
You forgot the part where the provider of your serverless charges you a multiple of what your idling server would cost you.
It’s basically slicing up a server and selling you some slices at an exaggerated premium.
You spend more on supervising the stuff running on the slices so they don’t bankrupt you when a peak happens than you would for maintaining a server.
But hey, it’s fashionable to be serverless so let’s all do it
so CGI
Yep. On someone else’s big pool of servers.
Easy, find the guy stuck with your old job, offer to take those servers off his hands.
Anon needs to reject technology and embrace luddism. Only then may he be free of oxymoron job roles.
Skill issue. The servers are abstracted away. All you’ve gotta do is not open the black box and it’s still serverless.
A little bit of water or a baseball bat would’ve saved his job
