Re:Serverless: slower and more expensive
by zinckiwi on Monday September 23, 2019 @08:51PM
(#21055392)
That's a fair observation. I do go back and forth but in the end it's enough to swing me, in the principle-of-least-regret way.
[ Parent
| on HN ]
Re:Serverless: slower and more expensive
by ufmace on Tuesday September 24, 2019 @02:26PM
(#21063173)
It seems like a pretty reasonable concern to me. We can presume the odds are pretty low, yeah. But the consequences are very high - you would need to redesign and possibly rewrite in another language your entire application. People complained up a storm about Reader dying, but it was a 5min process to export your subscriptions and import into another web reader that had basically the same feature set. Conventional Linux hosting, or even Docker, could be pretty easily re-hosted as-is on any of hundreds of other places.
Re:Serverless: slower and more expensive
by xchaotic on Monday September 23, 2019 @11:50PM
(#21056330)
So what do you use as the backend for now?
Re:Serverless: slower and more expensive
by zinckiwi on Thursday September 26, 2019 @03:47PM
(#21084753)
I usually go with a Django or RoR monolith, something that I know I can run on a cheap DO droplet or similar, and while there's a fixed monthly cost it's reasonable and I can scale up with ease (albeit manually). If I were explicitly needing the realtime DB aspect I'd probably look to Phoenix with the same hardware approach.