All terms
Glossary
Replatforming
A system is deliberately adapted to the platform during the move, without being rewritten.
Typical steps are replacing a self-run database with a managed service, moving file storage to object storage, and packaging applications into containers.
Effort sits between rehosting and rebuilding, and so does the benefit: less operations, real scaling, predictable cost, without taking the application apart.
How you notice it
- Databases are self operated, including backups and patching.
- Files sit on a file server instead of object storage.
- Operations consume more time than development.
Frequently asked
Where should replatforming start?
With the database, because that is where the operational load sits, and as its own step with a way back. Version differences and character sets only show up under load, so never combine it with the move itself.