zlacker

Seeing how it hasn't survived the HN hug of death... Not sure how you've built it but consider putting it behind a CDN or something and caching the responses, esp since you're trying to pull live data

>>hobo_i+(OP)
It was never down - it was being patched and redeployed based on feedback here.

Webapp is light enough to handle 10000 concurrent hits.

>>tinuvi+1C
I can't tell much about your infrastructure, but memcached would probably increase that by several orders of magnitude. The NGINX module is pretty simple: https://nginx.org/en/docs/http/ngx_http_memcached_module.htm...

Cloudflare with Cache-Control headers is even simpler if you're okay with adding Cloudflare as a dependency.

From an ASN lookup, it appears you're hosting on Oracle Cloud, so Cloudflare would also give you free data egress: https://blogs.oracle.com/cloud-infrastructure/why-cdn-client...

Their Always-On feature would also help if Oracle has an outage.

I like the general idea, very lightweight and more likely to remain accessible when an emergency is overloading the mobile networks.

>>decept+NF1
Thank you! I will implement this - the server code is in plain C with NGINX on top so I presume adding memached would be straightforward.