liveBook · Manning

Persistent data resource

As explained in Effective Platform Engineering

A persistent data resource is infrastructure that stores or manages data across application restarts, such as a database, message queue, file share, or cache.

A persistent data resource stores or manages data across application restarts, including databases, message queues, file shares, and high-performance caches. Platform teams expose these resources through an API so development teams receive a consistent provisioning experience while platform engineers retain operational responsibility. section 8.4.3

An operator-backed platform pattern typically:

  • Extends the Kubernetes API as the developer provisioning interface. section 8.4.3
  • Manages the operational lifecycle through infrastructure operators rather than treating resources as a simple wrapper for all infrastructure. section 8.4.3
  • Uses tools such as Crossplane, AWS ACK, Operator SDK, or Terraform Operator, each with an associated learning curve. section 8.4.3

Platform API for data infrastructure

An API team requests a database, message queue, file share, or high-performance cache through the Kubernetes API; the platform team provisions and operates the underlying resource through an operator. section 8.4.3

How Effective Platform Engineering covers it

How deep it goes
Defines resource categories and explains operator-based provisioning, while noting its distinct operational lifecycle and learning curve.
Examples
Uses databases, message queues, file shares, high-performance caches, Crossplane, AWS ACK, Operator SDK, and Terraform Operator.
What it assumes
Assumes familiarity with Kubernetes APIs and infrastructure lifecycle management, while distinguishing operators from traditional infrastructure as code.
What you can do after
Operate/configure persistent infrastructure through Kubernetes-backed operators while retaining platform ownership of its operational lifecycle.
How it connects
Connects databases, message queues, file shares, caches, Kubernetes APIs, infrastructure operators, and infrastructure as code.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.