CompactorRedirects without the machinery

Explanation

Read these pages when you need the reasoning behind Compactor's boundaries rather than a procedure or a field-level contract.

  • Architecture explains how HTTP orchestration, cached runtime lifecycle, and adapters remain separate.
  • Design philosophy describes the reliability choices behind startup validation and best-effort events.
  • Adapter model shows how to add storage integrations without coupling them to transport or cache behavior.
  • Why this is not a URL shortener helps adopters decide whether Compactor is the right product boundary.