81–90 of 167 posts
Earlier quoted context omitted.
Isn't the modern serverless just a "load on demand"-concept?
My intuition is: "Don't care where it runs, don't want to manage it, I want to pay only for when I actually use it, thanks for managing it, here's some extra cash for the effort"
Earlier quoted context omitted.
I think I will always struggle to understand the popularity of the term serverless. From the two definitions found in https://www.sqlite.org/serverless.html classic serverless --> "embedded database" exists and is often used neo-serverless --> I suspect that this is a marketing term used to attract cool people to new cloud offerings (like "jamstack" for services such as netlify). There is no good replacement here bec…
I wouldn't be surprised if the term originated as a marketing tactic (e.g., AWS) to seed in people's heads the idea of not having to care about servers
https://www.sqlite.org/serverless.html (first published 2007, before the more recent misuse of the term began)
Serverless is an adjective so you can slap it everywhere. Worker-based or FaaS (function as a service) don't roll off the tongue that well. I'm not advocating for the term, just trying to explain why it is so popular.
I've also experimented with this, unfortunately the 50ms CPU time isn't enough for datasets larger than 1.5MB. And the wasm init add at least 100ms to each request even when "hot" in cache. Also, out of a cost perspective, running a VM with SSD for cheap with SQlite will give much more requests than a CF worker for much less. Adding writes to this is also very limited due to the max 1sec write per KV key limit.
Earlier quoted context omitted.
I wouldn't be surprised if the term originated as a marketing tactic (e.g., AWS) to seed in people's heads the idea of not having to care about servers
You hit the nail on the head. It is all about marketing for the new front-end developers who don't want to learn "server side" manipulation db, files, etc. Personally the whole indexdb, localstorage really break the web page as a stateless model. Why do you need save so much local data to just maintain the session? Stop putting everything in the web browser.
What I'm curious is if (1) serverless is cheaper than hiring competent sysadmins who can maintain the infrastructure instead and (2) are these savings worth being locked into a chaotic architecture and boring proprietary tooling that is forced on you for the profit of the Google, Microsoft, and Amazon monopolies?
I've recently entered the job market and personally find no joy in working in serverless environments because of the latter.
https://www.sqlite.org/serverless.html (first published 2007, before the more recent misuse of the term began)
Earlier quoted context omitted.
> SQLite was already serverless. Yes but now it runs on someone else server! Wait a minute, this makes no sense... 'serverless' is perhaps the stupidest marketing buzzword developers have come up with.
Indeed it's quite stupid. Any alternative catchy name for the concept?
Earlier quoted context omitted.
You hit the nail on the head. It is all about marketing for the new front-end developers who don't want to learn "server side" manipulation db, files, etc. Personally the whole indexdb, localstorage really break the web page as a stateless model. Why do you need save so much local data to just maintain the session? Stop putting everything in the web browser.
I can see the value of serverless in general (not this hack necessarily) in small startups that don't have sysadmins on payroll but still want to rapidly deploy products with confidence that it will just work - all without worrying about infrastructure, scaling, etc. What I'm curious is if (1) serverless is cheaper than hiring competent sysadmins who can maintain the infrastructure instead and (2) are these savings w…
Earlier quoted context omitted.
Serverless is an adjective so you can slap it everywhere. Worker-based or FaaS (function as a service) don't roll off the tongue that well. I'm not advocating for the term, just trying to explain why it is so popular.
Also, serverless solutions like DynamoDB or S3 aren't compute, so worker based and FaaS would simply be wrong.