Data tiering keeps frequently accessed data in Kafka while moving older or less critical data to lower-cost storage. It helps organizations retain historical data without paying the full cost of keeping everything in the primary Kafka environment. section 18.4.2 section 18.6
A practical tiering arrangement separates recent operational access from historical retention:
- Keep frequently accessed data in Kafka for responsive retrieval by interested systems. section 18.4.2
- Offload older or less critical data to more cost-effective storage. section 14.4 section 18.6
- Plan retrieval across storage locations because data access can depend on its age. section 18.4.2
Recent events and historical events
An organization can retain recent event data in Kafka for systems that need near-real-time access, then move older historical events to lower-cost storage. This preserves long-term retention while requiring retrieval processes to account for where data resides. section 18.4.2 section 18.6
