One of our applications receive more than 10m hits a day through Kong, which uses Redis for its rate limit plugin. We put a t3.micro for that and never had any issue.
In reality, during our performance tests we got to much higher volumes and it always worked fine. What kind of issue with network did you encounter? Micro, small and medium should have the same network capacity.
So, t3.micros cost $7.4, yes, but if you do just 1 year no-upfront reservation it should be around $4.9 (it's usually a third in saving). I think the value proposition is too weak to even consider it, at least to me.
However, as someone else also mentioned, we need alternatives to other AWS services, those that are expensive enough to run them on prem.
The day you offer cheap Elasticsearch, ClickHouse, documentdb, etc, I'll kill my Hetzner machines and will come to you, sir.
However, as someone else also mentioned, we need alternatives to other AWS services, those that are expensive enough to run them on prem. The day you offer cheap Elasticsearch, ClickHouse, documentdb, etc, I'll kill my Hetzner machines and will come to you, sir.