liveBook · Manning

Backward compatibility

As explained in Vibe Engineering

Backward compatibility is the ability of a newer software version to preserve the behavior and interfaces expected by an older version's users or integrations.

Backward compatibility preserves the behavior, functionality, and access paths that existing users or integrations expect after a software change. During modernization, a visually similar replacement can still fail if customers’ remembered URLs stop working or if an AI tool removes an existing UI element while trying to simplify the application. section 2.7.1 section 2.2.4

Apply compatibility as an explicit migration contract:

  • Preserve existing functionality even when the replacement UI does not match the previous styling pixel for pixel. section 2.2.4
  • Keep established entry points available alongside new ones, because users and integrations may continue calling remembered URLs. section 2.7.1
  • State the requirement in prompts, assumptions, tests, and deployment checks rather than relying on generated code to infer it. section 2.7.1 section 2.2.4
  • Reject shortcuts that preserve source-code structure but create technical debt or make validation and diagnosis harder. section 7.3.1

A migration that keeps the old URL working

After migrating the application to Spring Boot, the old address http://localhost:8080/kitchensink/index.jsf remains reachable, while the new root address http://localhost:8080/kitchensink/ is also available. The UI remains almost identical, including the registered-members list that an earlier automated change removed. section 2.7.1

Figure 2.6 UI after migration to Spring Boot.

Use the migration figure to compare the resulting UI with the legacy application and assess whether the visible behavior remains acceptable. section 2.7.1

How Vibe Engineering covers it

How deep it goes
Defines compatibility through retained functionality and URLs, while deferring gradual dual-framework migration and exact visual matching.
Examples
Uses a Spring Boot migration, preserved registered-members UI, old and new web URLs, and a benchmark abstraction change.
What it assumes
Assumes knowledge of the legacy application's users, functionality, URLs, and deployment constraints.
What you can do after
Evaluate migrations by checking retained functionality, visible behavior, established URLs, and the maintainability of compatibility changes.
How it connects
Connects application migration with legacy modernization, user interfaces, web URLs, and deployment.

Also explained in

Compare how 22 books explain backward compatibility →

Related concepts

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