Show HN: I made an alternative to hosted Redis – Serverless for Redis
thiicket.com
thiicket.com
It’s almost like people don’t take security seriously.
Redis shouldn't grow infinitely. It should be memory bounded. Your code should expect evictions - in fact, almost every key in your redis cache should have an expiry.
Redis shouldn't be used over the internet like this anyway - you want colocated (in-datacenter) instances for sub-millisecond latency, otherwise what's the point?
RedisLabs IIRC also only offers encryption as an enterprise feature, which is something that has always left a bad taste in my mouth.
Yeah I didn't like this either, given how other "sexy" features that inherently mean you're not using a single instance listening on loopback were prioritised over TLS support. AFAIK their solution was essentially to run a TLS proxy in front of redis, and I'm not sure what they did if anything about any replicated traffic.
However, as of v6 (released recently) TLS is builtin.
As I explained in the discussion thread for the 6.0 announcement, putting a proxy in front of Redis, for clients that support TLS is like 10% of the problem, when you're using more than one instance. You end up creating a rats nest of tunnels and local port numbers, so that redis internal replication traffic, and internal sentinel traffic, and sentinel to redis traffic is all encrypted too.
One other point I forgot to mention - this is not an "alternative to hosted redis". It's still hosted redis, just with fancier jargon and more obscure guarantees. I can't imagine this being robust.
I'm not a devops guy so maybe i'm missing something obvious. On the other hand, I'm not a devops guy and I'm not _seeing_ an "obvious" win here. Either it actually doesn't meet my needs or I'm ignorant about something and the marketing isn't meeting my needs.
Side note: not a devops guy but my team has hundreds of AWS machines and lots of redis usage.
I don't know if that is what they're doing, but it's one possible thing they could be doing "better" (as in its an area that could be improved, not necessarily that it's fundamentally or technically possible/easy)
If your cloud function is running in say East Asia and your Redis instance is nearby, it will be much faster than querying your DB in Virginia.
You should really emphasize this in your marketing.