Taking over and re-architecting a booking platform

Quap is an online booking and customer-management platform. I took over the existing codebase and owned the full architecture across frontend and backend.

The platform was built on Phalcon, a framework with a shrinking pool of engineers who know it - a hiring and maintenance problem that compounds every year. Moving off it is straightforward to describe and easy to get wrong, because the booking flow is the business and cannot be paused for a rewrite.

• › Took over the existing codebase and established ownership of the architecture across frontend and backend.
• › Prepared the migration from Phalcon to Laravel on AWS, sequenced so the platform kept running.

Similar problem?