Re:Zerocal – A Serverless Calendar App in Rust
by jethro_tell on Thursday October 06, 2022 @04:30PM
(#33113676)
serverless is when you save the state but don't keep a machine sitting around when there are no requests, so you'd keep your calendar state in a hosted db and when someone asks for the calendar, a thread spins up and creates the calendar from the state and then disappears until there is another request. This is basically the exact opposite of serverless
[ Parent
| on HN ]
Re:Zerocal – A Serverless Calendar App in Rust
by rustyminnow on Thursday October 06, 2022 @04:56PM
(#33113988)
> serverless is when you [...] don't keep a machine sitting around when there are no requests
FTFY
The key part of serverless is that you don't have a server idling around. Whether or not you use a hosted db is not relevant.
Re:Zerocal – A Serverless Calendar App in Rust
by outworlder on Thursday October 06, 2022 @06:12PM
(#33114778)
And you may even use some 'serverless' DB services. Or not. The app is still serverless.
Re:Zerocal – A Serverless Calendar App in Rust
by drexlspivey on Thursday October 06, 2022 @04:39PM
(#33113798)
This can easily run on Cloudflare workers, you don't even need a server
Re:Zerocal – A Serverless Calendar App in Rust
by jcelerier on Thursday October 06, 2022 @06:11PM
(#33114763)
... what do you think those are
Re:Zerocal – A Serverless Calendar App in Rust
by vlovich123 on Thursday October 06, 2022 @09:16PM
(#33116286)
The generous interpretation of what op said is that you don’t have to maintain a server in any way or shape which is indeed the case. You only write business logic while the infrastructure automatically connects it to handle inbound requests.
Re:Zerocal – A Serverless Calendar App in Rust
by adamrezich on Thursday October 06, 2022 @06:34PM
(#33114997)
this thread is making me feel like I'm going crazy
Re:Zerocal – A Serverless Calendar App in Rust
by aliqot on Thursday October 06, 2022 @06:44PM
(#33115078)
Mmm yes, this one reminds me of the microservices debacle from a few years ago about when does your monolith technically become a microservice. I can't find the link, but I think we were unable to clearly define at which point your monolith has become a true 'SoA' group of microservices.