3 ms·
Very important caveats from the paper review at https://mikhail.io/2020/03/infinicache-distributed-cache-on-aws-lambda/ https://mikhail.io/2020/03/infinicache-d
by aaronbwebber 6y ago
Very important caveats from the paper review at https://mikhail.io/2020/03/infinicache-distributed-cache-on-aws-lambda/ https://mikhail.io/2020/03/infinicache-distributed-cache-on-...:
> Mind that the workload was selected to be a good match for InfiniCache properties (large objects with infrequent access).
> The hourly cost increases monotonically with the access rate, and eventually overshoots ElastiCache when the access rate exceeds 312 K requests per hour (86 requests per second).
So this is not a replacement for the most common use cases for Elasticache. It is interesting as a cache in front of S3, but if you want a cache in front of S3...just use Cloudfront?
Honestly if I was AWS I would be ecstatic if people used this, AWS probably breaks even or maybe loses a little bit on optimal usage of this, and makes an absolute killing if someone using this has a traffic spike and ends up hitting their lambda millions of times.