Apache Traffic Server
7.2#2 in caching softwareFree planFree planAPILinuxmacOSSelf-hosted
VisitApache Traffic Server vs Garnet
What both publish
| Fact | Apache Traffic Server | Garnet |
|---|---|---|
| Extensibility | Its plug-in APIs allow custom behavior such as modifying HTTP headers, handling ESI requests, or implementing a cache algorithm. | A custom operator framework lets developers register C# data structures and read-modify-write operations. |
| License | ATS is distributed under the OSI-approved Apache License 2.0. | The Garnet project is licensed under the MIT License. |
| Purpose | Apache Traffic Server is a fast, scalable, extensible HTTP/1.1 and HTTP/2 caching proxy server. | Garnet is a remote cache-store from Microsoft Research designed for high performance, extensibility, and low latency. |
| Security | Security options include client access controls, client authentication, SSL termination, and access control via SSL. | Garnet supports TLS/SSL connections and RESP password-based authentication. |
Apache Traffic Server plans
- Apache Traffic ServerFree
Garnet plans
- GarnetFree
- Azure Cosmos DB Garnet CachePriced on request
Pick Apache Traffic Server if…
Traffic Server suits organizations such as enterprises, internet service providers, backbone providers, and large intranets that need a caching proxy or reverse proxy. Its plugin APIs may also suit teams that need custom HTTP or cache behavior.
Pick Garnet if…
Garnet may suit developers seeking a self-hosted cache-store with RESP support, storage beyond memory, or multi-node clustering. Teams that need full Redis drop-in compatibility or Redis modules should note its stated limitations.