Lifecycle policy
A lifecycle policy is a set of rules governing data placement, retention, transition, archival, and deletion over time.
Architecting an Apache Iceberg Lakehouse
Data lifecycle management is the policy-based control of data placement, retention, deletion, archival, and tiering throughout its lifecycle.
- How it is used
- Coordinates storage placement, retention, deletion, archival, and tiering with lakehouse cost, governance, and compliance requirements.
- How deep it goes
- Explains policy dimensions and operational rationale, but stops short of vendor-specific rule syntax or implementation commands.
- Examples
- Uses StorageGRID, Amazon S3, Google Cloud Storage, Ceph, MinIO, storage classes, and Iceberg snapshot retention as examples.
- What you can do after
- Operate/configure lifecycle rules that automate tiering, archival, deletion, retention, and governance across lakehouse storage.
Read how Architecting an Apache Iceberg Lakehouse explains lifecycle policy →
Elasticsearch in Action, Second Edition
An Elasticsearch lifecycle policy is a set of rules that controls automatic index management, lifecycle phases, transitions, and actions.
- How it is used
- Automates rollover, retention, and index-management actions as indexes age, grow, or meet configured limits.
- How deep it goes
- Walks through policy definition, index and template association, rollover aliases, and a hot-warm-delete configuration.
- Examples
- Uses daily log indexes, a hot-delete policy, MySQL rollover indexes, and a hot-warm-delete policy.
- What you can do after
- Build it from scratch by defining an ILM policy and attaching it to an index or matching index template.
Read how Elasticsearch in Action, Second Edition explains lifecycle policy →
Microsoft Azure in Action
A lifecycle management policy is a set of rules that automatically performs data-management actions on storage objects based on conditions such as age or version age.
- How it is used
- Automates blob tier changes and deletion to reduce storage costs and support data retention.
- How deep it goes
- Works through JSON rules, age conditions, CLI deployment, policy combination, and verification; does not detail the policy engine.
- Examples
- Uses a book-storage account with 30- and 90-day tier transitions, optional 365-day deletion, and 90-day version cleanup.
- What you can do after
- Apply it via Azure CLI using a combined JSON policy, then verify the storage account’s configured policy.
Read how Microsoft Azure in Action explains lifecycle policy →
Related concepts
- index lifecycle managementconfigured by · Index lifecycle management is Elasticsearch functionality that automates index phases and actions based on conditions such as age, size, or document count.
- JSONconfigured by · JSON is a standardized, language-independent text format for representing structured data using objects, arrays, strings, numbers, Boolean values, and null.
- index rolloverconfigures · Index rollover is the replacement of a current Elasticsearch index with a new index while directing subsequent writes to the new index without copying existing documents.
- Elasticsearch indexconfigures · An Elasticsearch index is a named, searchable collection of documents organized for querying and distributed across storage shards and replicas.
- delete phasehas part · A delete phase is an index lifecycle stage in which an index is removed after preceding lifecycle phases complete.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.