liveBook · Manning

Sliding window

As explained in API Design Patterns

A sliding window is a bounded set of currently active versions that advances as newer versions replace older ones.

A sliding window keeps a bounded set of active API versions, advancing newer versions as older ones move toward removal. It reduces maintenance while delivering frequent functionality, but requires users to accept regular deprecations. section 24.3.2

Rolling version timeline

Version 1 begins as Preview, becomes Current in February, and is Deprecated in March. Meanwhile, Versions 2 and 3 advance behind it; by May, Version 1 is Deleted while Version 5 is Preview.

How API Design Patterns covers it

How deep it goes
Defines four lifecycle states and illustrates their progression, but does not detail implementation mechanics.
Examples
Uses a five-version monthly timeline and a state table covering Preview, Current, Deprecated, and Deleted.
What it assumes
Assumes API users can tolerate frequent deprecations and understand that Preview code may break without stability guarantees.
What you can do after
Operate/configure an API version lifecycle with explicit stability, change, deprecation, and deletion expectations.
How it connects
Connects API versioning with deprecation policy, compatibility, security patches, and critical bug fixes.

Also explained in

Compare how 5 books explain sliding window →

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.