v0.3.0

✨ Features

• Probabilistic Cache Refreshing (cache.refresh_percentage)
  • New configuration option under the cache section:

    cache:
      refresh_percentage: 10

  • Allows a percentage of requests to bypass the cache and fetch a fresh response from the backend.
  • Example: 10 means ~1 in every 10 requests to the same key will force a refresh.
  • Helps prevent stale data and reduces the need for manual invalidation.
  • Automatically re-stores the refreshed result in memory and persistent storage.

🐛 Fixes

• Fixed handling of root path /
  • The proxy now correctly forwards requests to / (previously may have failed or misrouted).
  • Fully compatible with downstream services expecting root-level access.

📊 Metrics & Internals

• Added debug logs and counters for refresh-triggered requests.
• cachebolt_memory_hits_total no longer counts requests that triggered a refresh.
• Refresh logic respects concurrency limits and latency-based failover rules.

🔄 Behavior

• If refresh_percentage is set to 0 or omitted, the cache will behave deterministically (no automatic refresh).
• Refresh logic is key-specific and probabilistic based on request counts.