liveBook · Manning

Hybrid migration approach

As explained in Vibe Engineering

A migration approach that combines in-place repository modification with work in a separate repository, retaining the legacy repository as a reference.

An in-place migration can lead AI to follow legacy structure, while a separate new repository can leave it without concrete business examples. A hybrid migration approach combines the strengths of both: it keeps the legacy repository as a reference and develops the modern application in a separate repository. section 2.3.1

Give each repository a clear role:

  • Treat a clone of the legacy repository as a read-only knowledge base for understanding existing flows and behavior, not as the long-term deployment source. section 2.3.1
  • Make the new repository the source of truth for the modern application. Define its modules, conventions, error handling, logging, API contracts, and domain boundaries up front. section 2.3.1

Give AI both the new architecture contract and relevant examples of old behavior. This provides business context without making the legacy structure the template for generated code. The separation is a guardrail, not a substitute for checking the result. section 2.3.1 section 2.12

Migrate gradually in tested, encapsulated increments. Increments that are too small make the workflow cumbersome; those that are too large become hard to review. Watch for AI-generated changes that infer future requirements, over-engineer the solution, or introduce bugs. section 2.12

Separate legacy reference and modern target

For a JBoss legacy application, retain a clone as the reference and scaffold a separate target using, for example, Spring Boot or Quarkus. Define modules such as api, app, domain, and infra before using legacy behavior to guide implementation. section 2.3.1

How Vibe Engineering covers it

How deep it goes
Defines repository roles and architectural guardrails, then recommends tested, reviewable migration increments.
Examples
Uses a JBoss legacy repository and a target scaffold with api, app, domain, and infra modules.
What you can do after
Evaluate repository roles and increment sizes for an AI-assisted migration.
How it connects
Connects legacy modernization with API contracts, domain boundaries, testing, and code review.

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.