Start with the service you need to preserve.
Identify the public pages, business rules, data and integrations behind one service. Compare the proposed architecture against those requirements before deciding how much to move.
Plan with your teamThe architecture decision
Change the foundation. Keep control.
Rebuilding selected services in Motoko removes the PHP runtime from those services. Understand the operating model, the work involved and the responsibilities your team keeps.
The Internet Computer
What changes in the operating model.
Patching keeps the PHP runtime in place. Rebuilding selected services in Motoko retires it from those services. The Internet Computer (ICP) runs the rebuilt application and stores the data you choose to move.
01 / Runtime
Remove the PHP engine.
Rebuilt features run without the PHP engine and its extensions. PHP components retained during the transition still need security updates, dependency review and monitoring.
Read PHP’s update guidance
02 / State
Replicate application data.
Application data is copied across a group of network computers called a subnet. The protocol coordinates accepted updates across those computers.
Explore the security model
03 / Delivery
Verify what is served.
Response certification lets a browser or gateway verify that content matches the application’s certified state. The delivery path must support this verification.
See response certificationYour team owns
Application logic, access controls, dependencies, upgrades, monitoring and data handling.
Read the security modelPatch the current deployment first.
Migration takes planning and validation. Keep the existing PHP application and its dependencies maintained while you evaluate and build the replacement.
Read the advisories and research