How to migrate a PHP monolith to a multi-service app with Node.js, Strapi, Next and Kubernetes
summary
A 2019 Symfony PHP monolith stays live while a new stack adds Next.js front ends, two BFFs (public and private) and a Node/Strapi back end that replaces session auth with JWT tokens and per‑partner keys; Strapi gains dozens of content types, components and admin plugins to cut customer‑service steps; Kubernetes and Traefik route requests between old and new pages and scale sites automatically; outcome: pages migrate incrementally, data integrity holds, partner APIs work and the combined system operates in production.
AI-written summary · about
related talks
30mApplication Modernization Using Cloud Strangler Pattern and DevOps Best Practices
40mDeploying node.js at scale
24mMicrofrontends
57mMigrating from a monolith to a new service
24mMigrating a Monolith to Kubernetes with Istio: Our Jou...
53mDeconstructing the monolith
19mMigrating from legacy platforms to node
34mMigrating a High‑Load Project to Microservices