Amazon ElastiCache vs Ehcache: What are the differences?
Developers describe Amazon ElastiCache as "Deploy, operate, and scale an in-memory cache in the cloud". ElastiCache improves the performance of web applications by allowing you to retrieve information from fast, managed, in-memory caches, instead of relying entirely on slower disk-based databases. ElastiCache supports Memcached and Redis. On the other hand, Ehcache is detailed as "Java's Most Widely-Used Cache". Ehcache is an open source, standards-based cache for boosting performance, offloading your database, and simplifying scalability. It's the most widely-used Java-based cache because it's robust, proven, and full-featured. Ehcache scales from in-process, with one or more nodes, all the way to mixed in-process/out-of-process configurations with terabyte-sized caches.
Amazon ElastiCache belongs to "Managed Memcache" category of the tech stack, while Ehcache can be primarily classified under "Cache".
Ehcache is an open source tool with 1.33K GitHub stars and 456 GitHub forks. Here's a link to Ehcache's open source repository on GitHub.
Airbnb, Instacart, and Asana are some of the popular companies that use Amazon ElastiCache, whereas Ehcache is used by Wongnai, Nuxeo, and Insoft. Amazon ElastiCache has a broader approval, being mentioned in 349 company stacks & 79 developers stacks; compared to Ehcache, which is listed in 4 company stacks and 8 developer stacks.
What is Amazon ElastiCache?
What is Ehcache?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon ElastiCache?
What are the cons of using Ehcache?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Ehcache?
We decided to use MemCachier as our Memcached provider because we were seeing some serious PostgreSQL performance issues with query-heavy pages on the site. We use MemCachier for all Rails caching and pretty aggressively too for the logged out experience (fully cached pages for the most part). We really need to move to Amazon ElastiCache as soon as possible so we can stop paying so much. The only reason we're not moving is because there are some restrictions on the network side due to our main app being hosted on Heroku.
I use a micro elesticache instance as a shared session store between the Node.js clusters of dojo.zerotoherojs.com and nightly.zerotoherojs.com
Audit the ElastiCache configurations for best practices and standards.