Apache Ignite VS Varnish

Ignite works as you describe: https://ignite.apache.org/ I wouldn't really recommend this approach, I would think more in terms of subscriptions and topics and less of a 'database'. - Source: Hacker News / about 2 years ago

Last days, I started using Apache Ignite as a cache strategy for some applications. Apache Ignite is an open-source In-Memory Data Grid, distributed database, caching, and high-performance computing platform. Source: over 2 years ago

Varnish Cache is a tool that provides a caching HTTP reverse proxy in order to accelerate your web applications. Once Varnish Cache is installed in front of any server that understands HTTP and configured to cache the contents, delivery speeds are typically enhanced by a factor of 300-1000x, depending on architecture. Kilobyte22 finds this tool along with HAProxy to be a winning combo. Source: 11 months ago

In this case, caching mechanism is situated in the proxy server or reverse proxy server like Nginx, Apache, or Varnish, and most probably it is a part of ISP (Internet Service Provider). - Source: dev.to / 12 months ago

To handle this level of traffic, you can use tools such as Varnish HTTP Cache, which caches the information of a news article starting from the first user who accesses and makes the request. Once Varnish caches the page, subsequent users will receive a response that is saved in memory. This process allows you to avoid unnecessary synchronous requests and send a quick response to users. - Source: dev.to / about 1 year ago

A couple of dedicated server-side resource caching solutions have emerged over the years: Memcached, Varnish, Squid, etc. Other solutions are less focused on web resource caching and more generic, e.g., Redis or Hazelcast. - Source: dev.to / over 1 year ago

Edge Side Includes (ESI): a more modern alternative to SSI. ESI can handle variables, have conditionals, and supports better error handling. ESI is supported by caching HTTP servers such as Varnish. - Source: dev.to / over 1 year ago