Live data from Hacker News

Why aren't we all serverless yet?

varoa.net

1–10 of 137 posts

Re: Why aren't we all serverless yet?

#3

they constantly try to escape from the complexity outside and within by dreaming of abstractions so perfect that no one will need to be good but the latency that is will shadow the "simple" that pretends to be

I've heard the noise of a virtual machine,

Now I'm stuck in the reality of backlash

And cashed–in chips.

Re: Why aren't we all serverless yet?

#5
> The median product engineer should reason about applications as composites of high-level, functional Lego blocks where technical low-level details are invisible. Serverless represents just about the ultimate abstraction for this mindset.

I think the answer is in the first sentence. A lot of engineers make products that don't touch the internet. This concept is lost in the noise quite a bit.

Re: Why aren't we all serverless yet?

#6
post #4

How about cost at scale? Amazon itself shifted Prime Video from serverless to mostly containers and it resulted in huge savings.

Without a link and a breakdown that makes no sense. We switched from blue to square and saw a honey suckle savings.

Amazon runs both and serverless is a billing model. Many serverless runtimes consume containers.

Serverless, like microservices are a design philosophy.

Re: Why aren't we all serverless yet?

#9
Because serverless doesn't exist. Serverless just means it runs on someone else's servers, just like the cloud. And 10 years down the road people have forgotten how to run basic things, but Bezos buys Panama.

Re: Why aren't we all serverless yet?

#10
This misses the main factor, I think: Vendor lock-in.

There is no unification of APIs - every provider has their own bespoke abstractions typically requiring heavy integration into further vendor-specific services - moreso if you are to leverage USPs.

Testing and reproducing locally is usually a pipe-dream (or take significantly more effort than the production deploy). Migrating to a different cloud usually requires significant rewrites and sometimes rearchitecturing.

Post reply on HN