Framework Portability Assessment

Snapshot: origin/main@e1eda106, assessed on 2026-06-07.

This guide captures what it would take to keep Quarkus as the existing runtime target while adding a Spring Boot portability path.

Recommendation

TPF should keep Quarkus as the mature reference, extract a neutral core, and add Spring behind explicit renderer/runtime adapter seams.

Guide Structure

• Coupling inventory
• Quarkus coupling
• Vert.x coupling
• Runtime split
• Reactive portability
• Persistence portability
• Annotation removal
• Code-generation portability
• Maven and scaffolding
• Roadmap and guardrails

The highest-value first slice remains: behavior-preserving runtime-core extraction with Quarkus adapters still owning CDI, Quarkus config, transport bindings, and Vert.x context bridging.