Replatform Strategy
You'll learn how replatforming lets you make targeted cloud optimizations during migration without overhauling your application's core architecture.
What is Replatforming?
Replatforming (sometimes called "lift-tinker-and-shift") sits between rehosting and full refactoring. While rehosting moves applications "as-is" to the cloud, replatforming makes tactical improvements during the migration to take advantage of cloud-native services—without rewriting your application's code or changing its fundamental design.
Think of it like moving to a new house and upgrading to smart thermostats and modern appliances during the move, but keeping the same floor plan and furniture arrangement.
Common Replatforming Changes
Typical optimizations include:
- Managed database services: Migrating from self-managed MySQL to Amazon RDS or Azure Database for MySQL
- Elastic compute: Moving to autoscaling groups instead of fixed VM counts
- Managed caching: Replacing self-hosted Redis with ElastiCache or Azure Cache
- Load balancer upgrades: Swapping legacy load balancers for cloud-native ALBs or Application Gateways
- Storage optimization: Moving file storage to object storage (S3, Blob Storage) where appropriate
When to Choose Replatforming
Replatforming makes sense when:
- Your application works well but needs better scalability or reduced operational overhead
- You want some cloud benefits without the time and risk of full refactoring
- Managed services can replace undifferentiated infrastructure tasks
- You're willing to accept minor configuration or connection string changes
The key is identifying high-value, low-risk improvements that don't require architectural changes.
Key Takeaway: Replatforming optimizes applications for the cloud through targeted service substitutions and configuration changes, delivering meaningful benefits without the complexity of rebuilding your architecture from scratch.