8 ms·
The linked issue talks about 1 req/s? That seems really reasonable to me, how was this a problem for your application or caused significant cost?
by jdndbsndn 2y ago
The linked issue talks about 1 req/s?
That seems really reasonable to me, how was this a problem for your application or caused significant cost?
- watermelon0 2y agoThat would still be 86k req/day, which can be quite expensive in a serverless environment, especially if the app is not optimized.
- Aeolun 2y agoThat’s a problem of the serverless environment, not of not being a good netizen. Seriously, my toaster from 20 years ago could serve 1req/s
- joshdavham 2y agoWhat would you recommend I do instead? Deploying a Docker container on Cloud Run sorta seemed like the logical way to deploy my micro app. Also for more context, this was the app in question (now moved to streamlit cloud): https://jreadability-demo.streamlit.app/ https://jreadability-demo.streamlit.app/
- ribadeo 2y agoSkip all that jazz and write some php like it's 1998 and pay 5 bucks a month for Hostens or the equivalent... Well, that's the opposite costing side of the spectrum from serverless containerized dynamic lang runtime and a zillion paid services as a backend.
- Saris 2y agoYour standard web hosting services, or a cheap VPS are great options. The whole 'cloud serverless buzzword-here' thing is ridiculous for most use cases. Heck you can serve quite a few static req/s on a $2 ESP32 microcontroller.
- _lvbh 2y ago1 req/s being too much sounds crazy to me. A single VPS should be able to handle hundreds if not thousands of requests per second. For more compute intensive stuff I run them on a spare laptop and reverse proxy through tailscale to expose it
- lanstin 2y agoWow that really works? So cool. I should bring my VMs back in house. Spare laptops I have.