Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Leaving serverless led to performance improvement and a simplified architecture

unkey.com

Post reply on HN
Print view View original

21–30 of 272 posts

Re: Leaving serverless led to performance improvement and a simplified architecture

#21

Post by johannes1234321 »

fabian2k wrote: post #6
pjmlp wrote: post #2

Their problem isn't serverless, rather Cloudflare Workers and WebAssembly. All major cloud vendors have serveless solutions based on containers, with longer managed lifetimes between requests, and naturally the ability to use properly AOT compiled languages on the containers.

At that point, why should I use serverless at all? If I have to think about the lifetime of the servers running my serverless functions?

For a thing, which permanently has load it makes little sense.

It can make sense if you have very differing load, with few notable spikes or on an all in on managed services, where serverless things are event collectors from other services ("new file in object store" - trigger function to update some index)

Re: Leaving serverless led to performance improvement and a simplified architecture

#22

Post by pjmlp »

fabian2k wrote: post #17
pjmlp wrote: post #11

Earlier quoted context omitted.

Because it is still less management effort than taking full control of the whole infrastructure. Usually a decision factor between more serverless, or more DevOps salaries.

I would doubt that this is categorically true. Serverless inherently makes the whole architecture more complex with more moving parts in most cases compared to classical web applications.

Depends pretty much where those classical web applications are hosted, how big is the infrasture taking care of security, backups, scalability, failovers, and the amount of salaries being paid, including on-call bonus.

Re: Leaving serverless led to performance improvement and a simplified architecture

#23

Post by kburman »

The takeaway here isn’t that serverless doesn’t work, it’s that the authors didn’t understand what they were building on. Putting a latency-critical API on a stateless edge runtime was a rookie mistake, and the pain they describe was entirely predictable.

Re: Leaving serverless led to performance improvement and a simplified architecture

#24

Post by pjmlp »

CuriouslyC wrote: post #12
pjmlp wrote: post #2

Their problem isn't serverless, rather Cloudflare Workers and WebAssembly. All major cloud vendors have serveless solutions based on containers, with longer managed lifetimes between requests, and naturally the ability to use properly AOT compiled languages on the containers.

Cloudflare has containers now too, and having used AppRunner and Cloud Run, it's much easier to work with. Once they get rid of the container caps and add more flexibility in terms of container resources, I would never go back to the big cloud containers, the price and ease of use of Cloudflare's containers just destroy them.

I doubt that the bill would be that much cheaper, nonetheless thanks for making me aware they are a thing now.

Re: Leaving serverless led to performance improvement and a simplified architecture

#25

Post by array_key_first »

pjmlp wrote: post #11
fabian2k wrote: post #6

Earlier quoted context omitted.

At that point, why should I use serverless at all? If I have to think about the lifetime of the servers running my serverless functions?

Because it is still less management effort than taking full control of the whole infrastructure. Usually a decision factor between more serverless, or more DevOps salaries.

There's a huge gap between serverless and full infra management. Also, IMO, serverless still requires engineers just to manage that. Your concerns shift, but then you need platform experts.

Re: Leaving serverless led to performance improvement and a simplified architecture

#27

Post by pjmlp »

array_key_first wrote: post #25
pjmlp wrote: post #11

Earlier quoted context omitted.

Because it is still less management effort than taking full control of the whole infrastructure. Usually a decision factor between more serverless, or more DevOps salaries.

There's a huge gap between serverless and full infra management. Also, IMO, serverless still requires engineers just to manage that. Your concerns shift, but then you need platform experts.

A smaller team, and from business point of view others take care of SLAs, which matters in cost center budgets.

Re: Leaving serverless led to performance improvement and a simplified architecture

#30

Post by seethishat »

wltr wrote: post #26
seethishat wrote: post #7

Linux servers running Go apps? Would be nice to see server cost and specs, backup strategy, etc.

Backup strategy? What do you mean by that?

Servers go down. What is the plan to get them "backup" and running ;)
Post reply on HN