liveBook · Manning

Statefulness

As explained in Google Anthos in Action

A stateful application retains client-session or other operational state that can affect subsequent requests.

Statefulness describes an application whose server stores client-session data, allowing the current transaction to be affected by previous transactions. section 15.4.3

Statefulness has direct deployment implications:

  • Route each request from a user to the same server when that server retains the relevant session state. section 15.4.3
  • Contrast stateful behavior with stateless applications, whose servers store no client-session knowledge or transaction history. section 15.4.3
  • Account for the distinction when interpreting migration-generated Kubernetes deployment specifications. section 15.4.3

How Google Anthos in Action covers it

How deep it goes
Defines statefulness through session retention and prior transactions, then stops short of detailing stateful deployment YAML.
Examples
Uses a migrated VM and generated deployment_spec.yaml to contrast stateful behavior with a stateless Kubernetes deployment.
What you can do after
Evaluate whether requests from a user must reach the same server during migration and deployment.
How it connects
Connects statefulness to stateless applications, client sessions, transactions, servers, Pods, Services, and Kubernetes deployments.

Also explained in

Compare how 14 books explain statefulness →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.