Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Zerocal – A Serverless Calendar App in Rust

endler.dev

Post reply on HN
Print view View original

41–50 of 64 posts

Re: Zerocal – A Serverless Calendar App in Rust

#41

Post by aliqot »

adamrezich wrote: post #38
jcelerier wrote: post #35

Earlier quoted context omitted.

... what do you think those are

this thread is making me feel like I'm going crazy

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.

Re: Zerocal – A Serverless Calendar App in Rust

#43

Post by aliqot »

belkarx wrote: post #28
tomcam wrote: post #21

Earlier quoted context omitted.

> I remember making things with Golang… was torture with common hosting solutions) What made it difficult to deploy Go apps?

I did it around 2 years ago: the web solutions were not very mature and it was poorly supported (but that's my subjective experience)

What solutions were you using?

Re: Zerocal – A Serverless Calendar App in Rust

#44

Post by actuallyalys »

omn1 wrote: post #25
EGreg wrote: post #23

Earlier quoted context omitted.

Sorry but how is it serverless? Is it a static HTML file with JS that does the job? Isn't there a server that the request goes to?

Good question. It depends on your definition of serverless. Strictly speaking there is no serverless, there's always some infrastructure somewhere. However the calendar file gets created out of thin air from the GET parameters alone. There is no state or storage involved. Other calendar apps have a backend with a DB; this one doesn't. Now whether that counts as truly serverless is up to you I guess. It's as close as…

"Stateless" is probably clearer. "Serverless" usually refers to services from cloud providers where your code is run on demand rather than having a server that is idling around (to use a sibling comment's phrase). I don't really care for "serverless" as a term because there are still servers (as you point out) and there are other architectures and cloud services that seem equally serverless that aren't usually called that.

Re: Zerocal – A Serverless Calendar App in Rust

#45

Post by chrisshroba »

aliqot wrote: post #43
belkarx wrote: post #28

Earlier quoted context omitted.

I did it around 2 years ago: the web solutions were not very mature and it was poorly supported (but that's my subjective experience)

What solutions were you using?

I’m also curious - could you maybe give an example of something concrete that is (or was) difficult in go but easy with rust?

Re: Zerocal – A Serverless Calendar App in Rust

#46

Post by Thaxll »

belkarx wrote: post #28
tomcam wrote: post #21

Earlier quoted context omitted.

> I remember making things with Golang… was torture with common hosting solutions) What made it difficult to deploy Go apps?

I did it around 2 years ago: the web solutions were not very mature and it was poorly supported (but that's my subjective experience)

What do you mean by web solution? Go ecosystem is mature in that field and it's very easy to deploy.

Re: Zerocal – A Serverless Calendar App in Rust

#48

Post by Thaxll »

omn1 wrote: post #25
EGreg wrote: post #23

Earlier quoted context omitted.

Sorry but how is it serverless? Is it a static HTML file with JS that does the job? Isn't there a server that the request goes to?

Good question. It depends on your definition of serverless. Strictly speaking there is no serverless, there's always some infrastructure somewhere. However the calendar file gets created out of thin air from the GET parameters alone. There is no state or storage involved. Other calendar apps have a backend with a DB; this one doesn't. Now whether that counts as truly serverless is up to you I guess. It's as close as…

Your app is always running to answer those GET so it's not serverless. Serverless means that your rust code would be invoked upon GET.

Re: Zerocal – A Serverless Calendar App in Rust

#49

Post by vlovich123 »

jcelerier wrote: post #35
drexlspivey wrote: post #30

Earlier quoted context omitted.

This can easily run on Cloudflare workers, you don't even need a server

... what do you think those are

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

#50

Post by belkarx »

aliqot wrote: post #43
belkarx wrote: post #28

Earlier quoted context omitted.

I did it around 2 years ago: the web solutions were not very mature and it was poorly supported (but that's my subjective experience)

What solutions were you using?

I was using Heroku, but thinking back it may have been just a factor of inexperience (I don't do web much, not had I used Heroku before and the UX is not great there). I can't actually remember which go framework I used, but I associate negative feelings with the experience (take this entire thing with a grain of salt - I just thought shuttle.rs + the general rust buildsystem seemed so much cleaner than what I recall doing - I struggled a lot with config files and getting the module system to work for me)
Post reply on HN