cache2k vs Varnish Cache

cache2k is an Apache-licensed, open-source library that keeps Java application objects in memory. Its project describes a JAR smaller than 400 KB with no external dependencies, and the implementation is written in pure Java without sun.misc.Unsafe. Cache behavior includes automatic expiry, refresh, refresh ahead, read-through loading, and event listeners. Cache loaders can suppress exceptions or retry them according to configuration. Integrations listed include Spring Framework, Scala Cache, DataNucleus through JCache, and Hibernate through JCache. cache2k supports JCache / JSR 107, while its guide notes extra overhead for that API compared with the native interface. Monitoring options include low-overhead statistics, JMX, and documented Micrometer metrics. Version 2 requires Java 8 or later and is described as compatible with Android API level 26. The library is free, available from Maven Central, self-hosted, and does not persist data.

Varnish Cache is a reverse caching proxy for Linux and self-hosted deployments. It serves cached responses from memory and sends other requests to origin servers. Its caching policy is defined in Varnish Configuration Language (VCL), which compiles to native code. Cached objects follow standard HTTP cache headers and leave the cache when they expire. Varnish supports TLS termination within the process and TLS connections to dynamic origin backends. It includes varnishlog for structured logging and varnishstat for metrics, and offers official container images and a Kubernetes Helm chart. Installation guidance covers Debian, Ubuntu, Red Hat Enterprise Linux, and compatible distributions. Varnish modules add functions callable from VCL. Its security guide describes controls at the command-line, CLI, VCL, and HTTP request levels. The free plan costs nothing. One limit to account for: Varnish avoids caching data when it cannot determine that doing so is safe, and applications may need configuration changes to reach a high cache hit rate.