The Point-to-Point migration pattern keeps separate API versions deployed in production, allowing consumers to migrate independently rather than coordinating one organization-wide cutover. section 4.10
The pattern shifts migration responsibility between consumers and providers:
- Consumers choose when to migrate, reducing the immediate time and cost of upgrading. section 4.10
- Some consumers may remain on an older version indefinitely if it continues to meet their needs. section 4.10
- Providers absorb the operational cost of maintaining several API services in production. section 4.10
- Compared with the Knot pattern, Point-to-Point reduces coordinated migration cost but can become more expensive than the Compatible pattern as versions accumulate. section 4.10
Figure 4.6 Jean-Jacques Dubray’s three models of API version migration. The cost of version migration for each model is illustrated in the chart. (Source: This is adapted from JJ’s original diagram available at https://mng.bz/0GON, along with the accompanying equations.)
Compare Point-to-Point with Knot and Compatible migration models using the cost illustration for growing numbers of API versions. section 4.10
