Converting a legacy app to API Platform
summary
A legacy Single Page App backend is rewritten to Symfony and API Platform while keeping the existing database schema and React consumers intact; the migration uses API Platform’s OpenAPI factory with oneOf and output DTOs to represent divergent responses, an automated test suite for API compatibility, and OpenAPI examples to document implicit payloads. The delivery builds an installable exe by using NSIS Docker pipeline to create a custom XAMPP bundle with PHP and frontend assets, supports upgrades from the old Python deployment, and the resulting installer and APIs work in production.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 1:34Legacy land challenges
- 4:19Deciding to rewrite
- 6:41Reasons for the migration
- 10:34Architecting the API
- 14:41Conquering the installer
- 18:53Conclusion and wrap-up
related talks
42mThe future of API (Platform) architecture
34mAPI Platform: From Rest & GraphQL APIs to state-of-the-art standards in seconds
43mModern Features in a Legacy App via APIs
43mSecure and Practical Authentication in API Platform
29mSingle Page Apps: What an API Developer Should Know
41mModernizing Legacy Apps - Platforms and Strategies
41mWhy your company needs an internal API and what you should do about it
42mSo You Want To Rewrite That...