Fighting vendor lock-in and designing testable serverless apps

Re:Fighting vendor lock-in and designing testable serverless... by slothario on Tuesday April 23, 2019 @09:37AM (#19728412)

It's fake work until your web application reaches a point where server loads take your web API down, and endpoints frequently take well over 10 seconds to respond.

Yes, I worked at a place where both of those things were true.

Switching some services out to a service (in this case, Azure functions) saved my company like $10k/mo, too.

[ Parent | on HN ]

Re:Fighting vendor lock-in and designing testable serverless... by dexen on Tuesday April 23, 2019 @09:46AM (#19728489)

This is a fine point. And yet both FB and Twitter managed to go through long period of servers being overloaded and fail-prone, to the point of frequent outages - cue the Fail Whale[1] - relatively unscathed, and emerge victorious.

In the end it's about taking calculated risks, and concentrating on where your effort and capital are most effective.

Virtually nobody thinks of the Fail Whale as a real risk now a day.

[1] https://pbs.twimg.com/media/DorDnbAU4AARTc3.jpg

[ Parent | on HN ]

Re:Fighting vendor lock-in and designing testable serverless... by lugg on Tuesday April 23, 2019 @11:18AM (#19729459)

Survivorship bias.

I'd also posit that there isn't much competition at the top.

[ Parent | on HN ]