4 ms·
I kind of love this idea. It reminds me of a redis use case we had at a former employer. We had a cluster with a high double digit number of nodes that delive
by kelp 5y ago
I kind of love this idea.
It reminds me of a redis use case we had at a former employer.
We had a cluster with a high double digit number of nodes that delivered a lot of data to various external APIs.
Some of those APIs required some metadata along with the payload. That metadata was large enough that it had made sense to cache it in Redis. But over time, with growth the cluster got large enough, and high volume enough that just fetching that data from Redis was saturating the 10Gbps Nic on the ElastiCache instance, creating a significant scaling bottleneck. (I don't remember if we moved up to the 25Gbps ones or not.)
But we could have just as easily done a local cache (on disk or something) for this metadata on each node and avoided the cost of the ElastiCache and all the scaling and operational issues. It would have also avoided the network round trips to Redis, and the whole thing probably would have just performed better.