souin

Souin is a high-performance HTTP cache system written in Go. It is designed to be used as middleware in various web frameworks and reverse proxies. It implements several key HTTP caching RFCs, including:

• RFC-2616
• RFC-7234
• RFC-9111
• RFC-9211
• Cache-Groups (draft)
• HTTP Cache invalidation (draft)

Souin is an HTTP cache system designed for use with reverse proxies. It can be deployed as a standalone component on top of existing proxies (like Apache or Nginx) or integrated directly as a plugin into proxies like Træfik, Caddy, or Tyk.

Key features include:

• RFC Compliance: Supports RFC-7234 (Vary, request coalescing, stale cache-control), the Cache-Status HTTP response header (RFC-9211), and Targeted HTTP Cache Control (RFC-9213).
• Modern Standards: Supports draft RFCs for http-cache-groups and http-invalidation.
• Advanced Capabilities: Supports ESI (Edge Side Includes) tags via the go-esi package and YKey grouping (similar to Varnish).
• Deployment: Written in Go, making it portable across any server, with Docker integration for Swarm or Kubernetes.

The Souin middleware for Webgo provides the following capabilities:

• RFC 7234 Compliance: Implements the standard HTTP Cache specification.
• Cache-Status Headers: Sets the Cache-Status HTTP Response Header to communicate cache state (e.g., HIT, MISS).
• REST API: Provides an API to purge specific items from the cache or list the resources currently stored.
• Distributed Caching: Built-in support for using distributed cache backends.
• Tag-based Invalidation: Allows invalidating groups of cached resources using tags.

The Souin Chi middleware provides the following capabilities:

• RFC 7234 Compliance: Implements the HTTP Cache specification.
• Cache-Status Header: Sets the Cache-Status HTTP Response Header to indicate cache hits, misses, or other states.
• REST API: Includes a REST API to purge specific cache entries and list currently stored resources.
• Distributed Caching: Built-in support for distributed cache backends.
• Tag-based Invalidation: Allows invalidating groups of cached resources using tags.

The Souin middleware for Dotweb provides the following capabilities:

• RFC 7234 Compliance: Implements the standard HTTP Cache specification.
• Cache-Status Header: Automatically sets the Cache-Status HTTP Response Header to indicate cache hits, misses, or other states.
• REST API: Includes a REST API to purge the cache and list currently stored resources.
• Distributed Caching: Built-in support for distributed cache implementations.
• Tag-based Invalidation: Supports invalidating cache entries using tags.

The Souin middleware for Goa provides the following capabilities:

• RFC 7234 Compliance: Implements standard HTTP caching specifications.
• Cache-Status Header: Automatically sets the Cache-Status HTTP Response Header to communicate cache hits/misses/etc.
• Cache Management: Provides a REST API to purge the cache and list stored resources.
• Distributed Caching: Built-in support for distributed cache backends.
• Tag-based Invalidation: Allows invalidating cache entries using specific tags.

The Souin Skipper plugin provides the following capabilities:

• RFC 7234 Compliance: Implements a standard-compliant HTTP Cache.
• Cache-Status Header: Automatically sets the Cache-Status HTTP Response Header to indicate cache hits/misses/etc., as per RFC specifications.
• Management API: Includes a REST API to purge the cache and list stored resources.
• Distributed Support: Built-in support for distributed cache environments.
• Invalidation: Supports tag-based cache invalidation.

The Souin Gin middleware provides the following capabilities:

• RFC 7234 Compliance: Implements the standard HTTP caching specification.
• Cache-Status Header: Automatically sets the Cache-Status HTTP Response Header to communicate cache results.
• Cache Management: Includes a REST API to purge the cache and list currently stored resources.
• Distributed Caching: Built-in support for distributed cache setups.
• Tag-based Invalidation: Allows invalidating cache entries using specific tags.

The Souin Echo middleware provides the following capabilities:

• RFC 7234 Compliance: Implements the standard HTTP Cache specification.
• Cache-Status Header: Sets the Cache-Status HTTP Response Header to indicate the cache state.
• REST API: Provides an API to purge the cache and list stored resources.
• Distributed Cache Support: Built-in support for distributed caching architectures.
• Tag-based Invalidation: Allows invalidating cache entries using tags.

The Souin Hertz middleware provides the following capabilities:

• RFC 7234 Compliance: Fully compliant HTTP caching behavior.
• Cache-Status Header: Sets the Cache-Status HTTP Response Header to indicate cache hits/misses.
• Cache Management: Includes a REST API to purge the cache and list stored resources.
• Distributed Caching: Built-in support for distributed cache backends.
• Tag-based Invalidation: Allows invalidating cache entries using specific tags.

The Souin Beego filter provides the following capabilities:

• RFC 7234 Compliance: Implements the standard HTTP caching specification.
• Cache-Status Header: Sets the Cache-Status HTTP Response Header to indicate cache hits, misses, or other states.
• REST API: Provides an API to purge the cache and list currently stored resources.
• Distributed Cache Support: Built-in support for using distributed cache backends.
• Tag-based Invalidation: Allows for invalidating groups of cached resources using tags.

The Souin Fiber middleware provides the following capabilities:

• RFC 7234 Compliance: Implements the standard HTTP caching specification.
• Cache-Status Headers: Automatically sets the Cache-Status HTTP Response Header to indicate cache hits, misses, or other states.
• Cache Management: Includes a REST API to purge specific resources or list all currently stored resources in the cache.
• Distributed Caching: Built-in support for distributed cache backends.
• Tag-based Invalidation: Allows for invalidating groups of cached resources using tags.