Project description
We have a large legacy application in PHP that has become a single monolith over the years. Within one codebase and one database live authorization, billing, catalog, notifications, and reports. The system has become hard to scale under load and painful to deploy: any minor change forces a redeploy of everything, and one slow query drags down even functions unrelated to it. A risky "rewrite from scratch" doesn't work for us. We need a careful staged migration where the product continues to work and make money at every step.
The foundation of the work is analysis before code. We expect you to describe the current behavior, identify clear bounded contexts, and together with us determine which module is safest to extract first. Each service should live behind a clear API contract, and the boundary should be introduced gradually so we can roll back if something goes wrong. We also need an asynchronous message queue so slow and bursty tasks stop blocking user requests, and containers so a service can be built, tested, and deployed separately.
Please propose a staged roadmap, not a single jump. A realistic plan for us starts with isolating one low-risk context, running it in parallel with the monolith, measuring the result, and only then moving forward. Honest compromises and clear explanations matter more than trendy words.
Scope of the first phase:
— Describe current modules and choose the first context to extract.
— Set the API contract and connect it to the monolith via a switch.
— Introduce a message queue for one asynchronous scenario.
— Containerize the extracted service with reproducible builds.
The foundation of the work is analysis before code. We expect you to describe the current behavior, identify clear bounded contexts, and together with us determine which module is safest to extract first. Each service should live behind a clear API contract, and the boundary should be introduced gradually so we can roll back if something goes wrong. We also need an asynchronous message queue so slow and bursty tasks stop blocking user requests, and containers so a service can be built, tested, and deployed separately.
Please propose a staged roadmap, not a single jump. A realistic plan for us starts with isolating one low-risk context, running it in parallel with the monolith, measuring the result, and only then moving forward. Honest compromises and clear explanations matter more than trendy words.
Scope of the first phase:
— Describe current modules and choose the first context to extract.
— Set the API contract and connect it to the monolith via a switch.
— Introduce a message queue for one asynchronous scenario.
— Containerize the extracted service with reproducible builds.
Software development Cash, Bank transfer
