[fifthofhisname]

> All data is offered for non-commercial use. With speedy APIs, all data can be served by just a couple of virtual machines for less than a coffee a day.

Very impressive! What does your backend stack look like? Are you using any caching or does every API call hit the binary file?

> The project went live 2 weeks ago and is slowly being used.

What kind of traffic are you getting?

Looking forward to future updates!

[meteo-jeff]

The API backend is written in Swift with some code in C (conversion Float16, interpolations, some solar radiation libraries). Data are read directly via mmap from local NVMe SSD disks. To scale, I can add new VMs and copy my binary files.

There is no frontend cache and I want to keep it this way. Next steps include point-of-presence API virtual machines in different counties. Via GeoDNS this is even faster than a CDN.

Peak API usage was around 50.000 API calls per hour, but on average it is quite low.

[ricksunny]

What would it take for it to also be offered on a commercial-use basis?

[meteo-jeff]

I do not actively prevent commercial use. I stated a non-commercial license as precaution to prevent all kinds of legal complications.

Mainly I also intent to reach open-source developers to make access to weather dat easier without the need to instruct users to sign-up for an API key somewhere.