Zend PHP to Node.js Migration
Budget: $250 – $750 USD
The existing backend is a medium-sized codebase (somewhere between 10 k and 100 k lines) written in PHP on the Zend framework. It currently powers user authentication and management, a set of JSON API services, and all read/write database operations. I now need the entire stack moved to Node.js while preserving every endpoint, data-flow rule, and security constraint already in place.
Please replicate the present behaviour one-to-one, keep response payloads unchanged so that the mobile and web front-ends remain unaffected, and deliver clean, well-documented code that can be unit- and integration-tested from day one. A short phased migration plan that minimises downtime will be expected up front, followed by staged hand-over of modules so QA can run in parallel with development.
Deliverables
• Architecture & migration plan outlining folder structure, chosen Node.js stack (Express, Koa, or similar) and session/auth strategy.
• Re-implemented Node.js code for authentication, API routing, and database layer, all functionally matching the Zend version.
• Automated tests and basic deployment scripts (Docker or simple CI) so the new service can be spun up identically in dev, staging, and production.
• Final knowledge-transfer session and concise technical documentation.
Please replicate the present behaviour one-to-one, keep response payloads unchanged so that the mobile and web front-ends remain unaffected, and deliver clean, well-documented code that can be unit- and integration-tested from day one. A short phased migration plan that minimises downtime will be expected up front, followed by staged hand-over of modules so QA can run in parallel with development.
Deliverables
• Architecture & migration plan outlining folder structure, chosen Node.js stack (Express, Koa, or similar) and session/auth strategy.
• Re-implemented Node.js code for authentication, API routing, and database layer, all functionally matching the Zend version.
• Automated tests and basic deployment scripts (Docker or simple CI) so the new service can be spun up identically in dev, staging, and production.
• Final knowledge-transfer session and concise technical documentation.