Kunstmaan Distributed Bundle Laravel Package

Product Decisions This Supports

• Scalability Roadmap: Enables distributed deployment of Kunstmaan CMS, critical for high-traffic or enterprise use cases where horizontal scaling is required.
• Build vs. Buy: Avoids reinventing distributed caching and cache invalidation logic, leveraging existing Redis-based solutions (snc/redis-bundle, predis/predis).
• Performance Optimization: Reduces filesystem I/O bottlenecks by replacing filesystem caching with Redis, improving response times in clustered environments.
• Content Management Use Cases: Supports headless CMS architectures or decoupled frontends (e.g., React/Vue) where cache consistency across nodes is non-negotiable.
• DevOps Alignment: Simplifies infrastructure setup for Kubernetes, Docker Swarm, or cloud auto-scaling by standardizing cache backends and invalidation strategies.

When to Consider This Package

• Adopt if:
  • Running Kunstmaan CMS on multi-server or containerized infrastructure (e.g., Kubernetes, Docker Swarm).
  • Requiring low-latency caching and cache invalidation for dynamic content (e.g., e-commerce, news sites).
  • Already using Redis in your stack (or willing to adopt it) for session storage or other caching needs.
  • Needing HTTP cache purging (e.g., for CDN or proxy invalidation via PURGE method).
• Look elsewhere if:
  • Your deployment is single-server or doesn’t require distributed caching.
  • You’re using alternative cache backends (e.g., Memcached, database-based caching).
  • Cache invalidation is handled via custom logic or third-party tools (e.g., Varnish, Fastly).
  • The package’s archived status (no stars/dependents) raises concerns about long-term maintenance (evaluate fork/alternatives like symfony/http-cache or liip/redis-cache).

How to Pitch It (Stakeholders)

For Executives: "This package lets us scale Kunstmaan CMS horizontally without sacrificing performance. By replacing slow filesystem caching with Redis—already in our stack—we’ll handle traffic spikes seamlessly while keeping content updates consistent across servers. It’s a low-risk, high-reward move to future-proof our CMS for growth, with minimal dev overhead."

For Engineering: *"The bundle provides two key wins:

1. Distributed caching: Swaps filesystem caches for Redis (via snc/redis-bundle), cutting I/O latency in clustered setups.
2. Cache invalidation: Adds a subscriber for page events to purge caches via HTTP PURGE (configurable for proxies/CDNs). Setup is straightforward: Add 3 bundles to AppKernel, configure Redis params, and define purge rules. Tradeoff: Archived repo (but logic is battle-tested in Kunstmaan’s ecosystem). Recommend pairing with a Redis HA setup for production."*