Hot data is recently generated or frequently accessed data that benefits from low-latency storage. In tiered storage, it remains on Kafka broker local disks while older data moves to cheaper remote storage. section 7.1.5
This arrangement balances access speed, retention, and cost:
- Keep frequently accessed data local for low-latency reads. section 7.1.5
- Move older, rolled-over segments and metadata to Amazon S3, Azure Blob Storage, Google Cloud Storage, or another remote system. section 7.1.5
- Let consumers use normal operations without knowing whether requested data is local or remote. section 7.1.5
Figure 7.13 When the tiered storage feature is enabled, the cold data is moved periodically to cheaper, cloud-based storage.
Shows hot data remaining on broker disks while cold data is periodically offloaded to cheaper cloud storage. section 7.1.5
