71–80 of 167 posts
https://www.sqlite.org/serverless.html (first published 2007, before the more recent misuse of the term began)
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.
https://www.sqlite.org/serverless.html (first published 2007, before the more recent misuse of the term began)
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 was thinking of making it possible for SQLite to be used with static pages. My idea is to modify SQLite to use ajax with the HTTP Range header to fetch B+ pages from the server as they are needed. SQLite already has a VFS (virtual file system) so this shouldn't be too hard. I am not sure how fast it would be and it would waste a lot of bandwidth. That's why I haven't made it yet. This would only be useful for using…
Have you seen http://sigusr2.net/serving-traffic-directly-from-sqlite.html ?
Earlier quoted context omitted.
It's the future of the web they said! Seriously though, if it's Truing complete, you know it'll be abused to do something completely unintended, like run a ray tracer or something.
Ray tracing in lambda could be cool... perfect candidate for horizontal scale... lambda per pixel?
Earlier quoted context omitted.
"Shared hosting".
I would agree and here's why: when compared to PHP scripts of old, the concept is the same. You have some bit of executable code that gets called when a specific URL is hit.
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
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.
Earlier quoted context omitted.
Indeed it's quite stupid. Any alternative catchy name for the concept?
Isn't the modern serverless just a "load on demand"-concept?
"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"