Why aren't we all serverless yet?
varoa.net
Why aren't we all serverless yet?
1–10 of 137 posts
Re: Why aren't we all serverless yet?
#2from 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
Re: Why aren't we all serverless yet?
#3they 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
Now I'm stuck in the reality of backlash
And cashed–in chips.
Re: Why aren't we all serverless yet?
#4Re: Why aren't we all serverless yet?
#5I 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?
#6How about cost at scale? Amazon itself shifted Prime Video from serverless to mostly containers and it resulted in huge 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?
#7Re: Why aren't we all serverless yet?
#8Re: Why aren't we all serverless yet?
#9Re: Why aren't we all serverless yet?
#10There 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.