Apache Traffic Server vs Ehcache
Apache Traffic Server
trafficserver.apache.orgEhcache
ehcache.orgSide by side
| Figure | Apache Traffic Server | Ehcache |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | Yes | Yes |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 3 |
| Spec score · Caching Software | 8.9 (#2) | 8.5 (#4) |
| Installation | The project distributes source tarballs and repository code rather than project-provided binary downloads; installation uses CMake. | Ehcache 3.11.1 can be added with Maven or Gradle using org.ehcache:ehcache:3.11.1. |
| Maker headquarters | LinkedIn lists the foundation headquarters as Wilmington, Delaware. | LinkedIn lists Terracotta headquarters in San Francisco, California. |
| Purpose | Apache Traffic Server is a fast, scalable, extensible HTTP/1.1 and HTTP/2 caching proxy server. | Ehcache is an open-source, standards-based Java cache that boosts performance, offloads databases, and simplifies scalability. |
| Support | Users can seek help through the Users Mailing List or ASF Slack, and code questions through the developers discussion list. | Ehcache documentation directs users with unanswered questions to its support forums. |
| What it does | Apache Traffic Server is a fast, scalable and extensible HTTP/1.1 and HTTP/2 caching proxy. | Ehcache is a Java cache intended to improve application speed, reduce database load and support scalable deployments. |
Plans
In their own words
Apache Traffic Server
Apache Traffic Server is a free, open-source caching proxy server for HTTP/1.1 and HTTP/2. It stores frequently requested pages, images, and web service calls so they can be reused, with the stated aims of improving response time and reducing server load and bandwidth needs. It can also add keep-alive behavior, filter or anonymize requests, and balance traffic through a proxy layer. Deployment patterns include web proxy cache, reverse proxy, and cache hierarchy. As a layer 7 HTTP load balancer, it can choose next-hop servers using request attributes, weighted round robin, or URL consistent hashing. Plug-in APIs let teams add behavior such as changing headers, handling ESI requests, or implementing cache algorithms. Security options include client access controls and authentication, SSL termination, and SSL-based access control. It is self-hosted, with Linux and macOS listed as platforms. The project identifies enterprises, internet service providers, backbone providers, and large intranets as its intended audience. The listed stable release is 10.2.0; 9.2.15 is listed as the long-term support release.
Ehcache
Ehcache is a free, open-source Java caching library for keeping application data, database results, and web pages available to applications. It is designed to improve performance, reduce database work, and support scaling. It can run inside an application or in mixed in-process and out-of-process deployments, including terabyte-sized caches. Ehcache 3 supports off-heap storage, including configurations that rely on it exclusively, and is compatible with the JCache API defined by JSR-107. The project describes Spring Caching and Hibernate integration through javax.cache support. Configuration is available through XML or the Java API, and data can be shared between application instances using Terracotta clustered storage. Ehcache 3.11 also allows caches to share resources. It supports JTA-managed XA transactions, including two-phase commit and crash recovery, but documents Read-Committed as the only supported isolation level and Bitronix 2.1.4 as the only tested transaction manager. Ehcache 3.11 requires Java 8 or later and is the last release line to support Java 8. The license is Apache 2.0.