Need advice about which tool to choose?Ask the StackShare community!

Ehcache

513
150
+ 1
4
Hazelcast

333
447
+ 1
59
Add tool

Ehcache vs Hazelcast: What are the differences?

Developers describe Ehcache 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. On the other hand, Hazelcast is detailed as "Clustering and highly scalable data distribution platform for Java". With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution.

Ehcache and Hazelcast are primarily classified as "Cache" and "In-Memory Databases" tools respectively.

Ehcache and Hazelcast are both open source tools. Hazelcast with 3.18K GitHub stars and 1.16K forks on GitHub appears to be more popular than Ehcache with 1.33K GitHub stars and 456 GitHub forks.

According to the StackShare community, Hazelcast has a broader approval, being mentioned in 26 company stacks & 16 developers stacks; compared to Ehcache, which is listed in 4 company stacks and 8 developer stacks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Ehcache
Pros of Hazelcast
  • 1
    Way Faster than Redis and Elasticache Redis
  • 1
    Easy setup
  • 1
    Simpler to run in testing environment
  • 1
    Container doesn't have to be running for local tests
  • 11
    High Availibility
  • 6
    Distributed Locking
  • 6
    Distributed compute
  • 5
    Sharding
  • 4
    Load balancing
  • 3
    Map-reduce functionality
  • 3
    Simple-to-use
  • 3
    Written in java. runs on jvm
  • 3
    Publish-subscribe
  • 3
    Sql query support in cluster wide
  • 2
    Optimis locking for map
  • 2
    Performance
  • 2
    Multiple client language support
  • 2
    Rest interface
  • 1
    Admin Interface (Management Center)
  • 1
    Better Documentation
  • 1
    Easy to use
  • 1
    Super Fast

Sign up to add or upvote prosMake informed product decisions

Cons of Ehcache
Cons of Hazelcast
    Be the first to leave a con
    • 4
      License needed for SSL

    Sign up to add or upvote consMake informed product decisions

    What is Ehcache?

    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.

    What is Hazelcast?

    With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Ehcache?
    What companies use Hazelcast?
    See which teams inside your own company are using Ehcache or Hazelcast.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Ehcache?
    What tools integrate with Hazelcast?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      What are some alternatives to Ehcache and Hazelcast?
      Memcached
      Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.
      Apache Ignite
      It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale
      Redis
      Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.
      guava
      The Guava project contains several of Google's core libraries that we rely on in our Java-based projects: collections, caching, primitives support, concurrency libraries, common annotations, string processing, I/O, and so forth.
      GraphQL Cache
      A custom middleware for graphql-ruby that handles key construction and cache reads/writes transparently.
      See all alternatives