[sikhnerd]

I'll pile on here as well, we were thinking about shifting from elasticache to RL, but this has made that decision super easy.

[fizzybeetle]

Elasticache is a totally closed source implementation that does not contribute back to the community. How did this situation change your decision?

[dilap]

what would they contribute back? elasticache is just vanilla redis. aws is selling you compute time and ram.

[scrollaway]

> elasticache is just vanilla redis

Only at the interface level. Elasticache is a heavily forked Redis. There's a reason it's several versions behind.

[dilap]

that makes sense. i guess i had just assumed it was laziness. :-)

out of curiosity, do you have any idea what their mods might be?

[scrollaway]

I never bothered to really look into it -- I suspect it's semi-public information. If I had to guess, lots of internal changes to make Redis behave better in AWS's architecture to do with containerization, EC2, S3/EBS, maintenance automation related stuff, instrumentation, etc.

Oh actually definitely some stuff related to their redis clustering system.

[buzer]

They also support encryption in transit. That part was open sourced recently, but hasn't made it into upstream yet (though it most likely will from sounds of it).