You don't need a database, just an in-memory cache. All you're storing is recent weather info, which you get from an external server. Caching is just to prevent hitting the external server too hard.
Then the program becomes a single-file executable, which means you can get rid of Docker.
If you set this up to run under FCGI, it can run on some $5/month shared hosting account.
I think this over complication makes the comparison more realistic. Yes for this exact example it's too much, but it gives a better understanding of what a more complex real-world example would look like.
Comments
Both are amusingly over-complicated.
You don't need a database, just an in-memory cache. All you're storing is recent weather info, which you get from an external server. Caching is just to prevent hitting the external server too hard.
Then the program becomes a single-file executable, which means you can get rid of Docker.
If you set this up to run under FCGI, it can run on some $5/month shared hosting account.
I think this over complication makes the comparison more realistic. Yes for this exact example it's too much, but it gives a better understanding of what a more complex real-world example would look like.
This isn't a case study on how to build a weather app. It's okay to include unnecessary features to showcase how the language uses them.
You can get rid of Docker either way.