Customer story · Amazon EKS migration
Waydev: migration to Amazon EKS with 45% lower infrastructure costs.
CloudHero migrated Waydev’s PHP application to Amazon EKS and its MySQL database to Amazon Aurora. The published customer story reports a migration in less than two hours and a 45% reduction in infrastructure costs within two months.
- Platform
- Amazon EKS and Aurora
- Reported migration window
- Less than two hours
- Reported infrastructure costs
- 45% lower within two months
The starting point
Why did Waydev migrate to Amazon EKS?
Waydev needed a more stable platform for its software engineering analytics product. Its PHP monolith ran on virtual servers alongside a self-managed MySQL database. Infrastructure incidents, slow releases and scaling constraints were taking time away from product development.
The work covered application containerization, a move to Amazon Elastic Kubernetes Service (Amazon EKS), migration from MySQL to Amazon Aurora, and infrastructure provisioning through Terraform. Waydev wanted repeatable deployments, autoscaling and managed services, with a stronger approach to backups and operations.
The original project also identified SOC 3 as an objective. This case study describes the infrastructure work; it does not establish the outcome or current status of Waydev’s independent assurance process.
Engineering decisions
What changed in the application and database platform?
CloudHero containerized Waydev’s workloads and deployed the application stack on Amazon EKS. The database moved from self-managed MySQL to Amazon Aurora. Terraform captured the infrastructure as code so the environment could be provisioned and changed through a repeatable process.
| Before the migration | Delivered with CloudHero |
|---|---|
| PHP monolith on virtual servers | Containerized workloads deployed on Amazon EKS |
| Self-managed MySQL | Amazon Aurora managed database |
| Infrastructure provisioning to streamline | Terraform infrastructure as code and GitOps practices |
| Scaling and operational constraints | Kubernetes autoscaling and AWS managed services |
The project account also records Amazon EC2, Amazon S3, AWS Identity and Access Management (IAM), Amazon CloudWatch and AWS CloudTrail. CloudHero’s Lift and Shift to EKS listing on AWS Marketplace identifies Waydev’s use of EKS and KEDA for autoscaling processing pipelines. That listing is CloudHero’s own published description of the solution.
The migration
What did the two-hour migration include?
The published customer account describes the move to AWS taking less than two hours after an incident at the previous provider prompted the team to bring the migration forward. This was the migration execution window. Assessment, containerization and preparation of the target environment were separate work.
- Assess and prepare. Review the existing application and infrastructure, then containerize the workloads.
- Build the target environment. Prepare the AWS landing zone and deploy the application stack on EKS, with infrastructure managed through Terraform.
- Move application and database workloads. Migrate the application to AWS and the MySQL database to Amazon Aurora.
- Optimize after migration. Refine performance, security and cost management in the new environment.
The original account names CloudHero’s Migy assessment, Squid containerization assessment and Captain landing-zone automation tools as part of the migration approach.
“Together with CloudHero, we performed the entire migration to AWS in less than two hours.”
Hear the customer’s perspective
In CloudHero’s customer interview, Alex Circei, CEO and co-founder of Waydev, discusses the Kubernetes engagement.
Reported outcomes
What results did Waydev report after the migration?
CloudHero’s original Waydev case study reports a 45% reduction in infrastructure costs within two months, fewer downtime-generating events and faster recovery. The figures below describe the historical project and retain the measures used in that account.
| Measure | Reported result |
|---|---|
| Infrastructure costs | 45% reduction within two months |
| Downtime-generating events | 95% reduction |
| Mean time to recovery (MTTR) | From over two hours to under four minutes |
| Developer productivity | 85% improvement |
Source: CloudHero’s original Waydev project account. The published account does not include the underlying billing dataset, incident sample or productivity measurement method. These figures are reported project outcomes, not independently remeasured results or a forecast for another migration.
Plan your own migration
What should your team establish before moving to EKS?
Use Waydev’s story to frame the application, database and operational work together. A migration plan needs to account for dependencies, data transfer, release practices and the team that will run the platform after the move.
- Separate the assessment and preparation schedule from the production migration window.
- Agree how application behavior, database consistency and rollback will be checked.
- Define the baseline and measurement period for costs, incidents and recovery time.
- Choose Kubernetes and managed services around the workload and the team’s operating requirements.
These are planning questions for your project. Explore our AWS migration services and Kubernetes and Amazon EKS engineering, or review the application modernization assessment.