Behind-the-scenes work to keep Hollahoop fast and stable under load.

• Shared rate limiting and hot-read caching across all app instances (so limits are exact and survive deploys), with a clean fallback when the cache is unavailable.
• Edge caching and CDN-friendly headers for public pages and media, cutting origin load during traffic spikes.
• Verified and tuned Postgres connection pooling so database connections stay bounded under heavy traffic.

You should not notice anything except snappier pages and steadier performance when things get busy.