liveBook · Manning

Agile instability

As explained in API Design Patterns

Agile instability is an API versioning strategy that maintains a small sliding window of versions and frequently deprecates older versions to deliver new functionality quickly.

Agile instability keeps a small sliding window of API versions, trading long-term stability for lower maintenance overhead and faster delivery of new functionality. It suits active, engaged users who can absorb frequent deprecations. section 24.3.2

A rolling version window

A typical timeline places version 1 in Preview during January, Current in February, Deprecated in March, and Deleted in May. Meanwhile, newer versions successively occupy Preview and Current, maintaining a moving development window.

How API Design Patterns covers it

How deep it goes
Explains four lifecycle states and their change policies, then illustrates their monthly progression without implementation details.
Examples
Uses a five-month timeline in which five versions rotate through Preview, Current, Deprecated, and Deleted.
What you can do after
Evaluate API version lifecycles and the trade-off between rapid functionality and frequent client migrations.
How it connects
Connects API versioning to deprecation policy, client compatibility, security patches, and critical bug fixes.

Related concepts

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