Services

Resources

Company

Our Work

Blog

#Cloud-Migration

Back to Tags

Case Studies

Migrating Monolith Application to Cloud Native Stack

The client provides cloud and on-premise based Hospital Management Services (HMS) SaaS platform. This HMS serves 800+ B2B customers (tenants), including large hospital chains across the Middle East, Africa, and APAC region. The tech stack for the application is a Java-based backend, JSP-based server rendered UI, Redis, and MySQL as datastores. The HMS platform is deployed as a SaaS and in customers' cloud environments and on-premise data centers.

Learn More

Migrating Monolith Application to Cloud Native Stack

The client provides cloud and on-premise based Hospital Management Services (HMS) SaaS platform. This HMS serves 800+ B2B customers (tenants), including large hospital chains across the Middle East, Africa, and APAC region. The tech stack for the application is a Java-based backend, JSP-based server rendered UI, Redis, and MySQL as datastores. The HMS platform is deployed as a SaaS and in customers' cloud environments and on-premise data centers.

Learn More

Migrating Monolith Application to Cloud Native Stack

The client provides cloud and on-premise based Hospital Management Services (HMS) SaaS platform. This HMS serves 800+ B2B customers (tenants), including large hospital chains across the Middle East, Africa, and APAC region. The tech stack for the application is a Java-based backend, JSP-based server rendered UI, Redis, and MySQL as datastores. The HMS platform is deployed as a SaaS and in customers' cloud environments and on-premise data centers.

Learn More

Migrating Monolith Application to Cloud Native Stack

The client provides cloud and on-premise based Hospital Management Services (HMS) SaaS platform. This HMS serves 800+ B2B customers (tenants), including large hospital chains across the Middle East, Africa, and APAC region. The tech stack for the application is a Java-based backend, JSP-based server rendered UI, Redis, and MySQL as datastores. The HMS platform is deployed as a SaaS and in customers' cloud environments and on-premise data centers.

Learn More

Migrating 1.3TB of Primary Data from Self-Hosted MySQL to GCP CloudSQL

Problem Statement. Build an automated backup and recovery process for the SIEM data Provide administrative controls for customizing the backup and restore options Implement tenant-wise customizations for data retention, data locality, and other parameters

Learn More

Migrating 1.3TB of Primary Data from Self-Hosted MySQL to GCP CloudSQL

Problem Statement. Build an automated backup and recovery process for the SIEM data Provide administrative controls for customizing the backup and restore options Implement tenant-wise customizations for data retention, data locality, and other parameters

Learn More

Migrating 1.3TB of Primary Data from Self-Hosted MySQL to GCP CloudSQL

Problem Statement. Build an automated backup and recovery process for the SIEM data Provide administrative controls for customizing the backup and restore options Implement tenant-wise customizations for data retention, data locality, and other parameters

Learn More

Migrating 1.3TB of Primary Data from Self-Hosted MySQL to GCP CloudSQL

Problem Statement. Build an automated backup and recovery process for the SIEM data Provide administrative controls for customizing the backup and restore options Implement tenant-wise customizations for data retention, data locality, and other parameters

Learn More

Migrating from Heroku PaaS to AWS

When ADPList approached us, they had an immediate problem at hand. The latency for the business critical APIs was high and caused poor user experience. Before anything else, we started focusing on solving that problem. The entire stack for ADPList was running on Heroku. To improve performance, the ADPList team already implemented vertical infrastructure scaling. However, this resulted in a massive increase in costs. Apart from the costs, we realized that Heroku isn’t particularly suited well for microservices deployments at ADPList due to:

300%

Application performance improvement

50%

Cost reduction

3x

Throughput improvement

Migrating from Heroku PaaS to AWS

When ADPList approached us, they had an immediate problem at hand. The latency for the business critical APIs was high and caused poor user experience. Before anything else, we started focusing on solving that problem. The entire stack for ADPList was running on Heroku. To improve performance, the ADPList team already implemented vertical infrastructure scaling. However, this resulted in a massive increase in costs. Apart from the costs, we realized that Heroku isn’t particularly suited well for microservices deployments at ADPList due to:

300%

Application performance improvement

50%

Cost reduction

3x

Throughput improvement

Migrating from Heroku PaaS to AWS

When ADPList approached us, they had an immediate problem at hand. The latency for the business critical APIs was high and caused poor user experience. Before anything else, we started focusing on solving that problem. The entire stack for ADPList was running on Heroku. To improve performance, the ADPList team already implemented vertical infrastructure scaling. However, this resulted in a massive increase in costs. Apart from the costs, we realized that Heroku isn’t particularly suited well for microservices deployments at ADPList due to:

300%

Application performance improvement

50%

Cost reduction

3x

Throughput improvement

Migrating from Heroku PaaS to AWS

When ADPList approached us, they had an immediate problem at hand. The latency for the business critical APIs was high and caused poor user experience. Before anything else, we started focusing on solving that problem. The entire stack for ADPList was running on Heroku. To improve performance, the ADPList team already implemented vertical infrastructure scaling. However, this resulted in a massive increase in costs. Apart from the costs, we realized that Heroku isn’t particularly suited well for microservices deployments at ADPList due to:

300%

Application performance improvement

50%

Cost reduction

3x

Throughput improvement

Migrating from Heroku PaaS to AWS

When ADPList approached us, they had an immediate problem at hand. The latency for the business critical APIs was high and caused poor user experience. Before anything else, we started focusing on solving that problem. The entire stack for ADPList was running on Heroku. To improve performance, the ADPList team already implemented vertical infrastructure scaling. However, this resulted in a massive increase in costs. Apart from the costs, we realized that Heroku isn’t particularly suited well for microservices deployments at ADPList due to:

300%

Application performance improvement

50%

Cost reduction

3x

Throughput improvement

A funnel icon represents the limitations of VMs. They are not as scalable or agile as containerized applications. Scaling a VM requires provisioning a whole new server, while scaling a containerized application simply involves spinning up more containers.

Journey of moving VM-based workloads to Kubernetes

Flip is a fintech company in Indonesia. We migrated their stateless services running on 25+ VMs in the Alibaba cloud to their managed Kubernetes offering (ACK). These application services served Flip's B2B and B2C traffic which often peaked at 25,000 requests/second. Problem Statement. Implement autoscaling of the infrastructure to handle peak traffic. Move to a Cloud-Native architecture to use modern tooling. Solve the problems related to configuration management and operational toil.

30%

Cost Saved

120

Pods at peak load

0sec

Downtime

A funnel icon represents the limitations of VMs. They are not as scalable or agile as containerized applications. Scaling a VM requires provisioning a whole new server, while scaling a containerized application simply involves spinning up more containers.

Journey of moving VM-based workloads to Kubernetes

Flip is a fintech company in Indonesia. We migrated their stateless services running on 25+ VMs in the Alibaba cloud to their managed Kubernetes offering (ACK). These application services served Flip's B2B and B2C traffic which often peaked at 25,000 requests/second. Problem Statement. Implement autoscaling of the infrastructure to handle peak traffic. Move to a Cloud-Native architecture to use modern tooling. Solve the problems related to configuration management and operational toil.

30%

Cost Saved

120

Pods at peak load

0sec

Downtime

A funnel icon represents the limitations of VMs. They are not as scalable or agile as containerized applications. Scaling a VM requires provisioning a whole new server, while scaling a containerized application simply involves spinning up more containers.

Journey of moving VM-based workloads to Kubernetes

Flip is a fintech company in Indonesia. We migrated their stateless services running on 25+ VMs in the Alibaba cloud to their managed Kubernetes offering (ACK). These application services served Flip's B2B and B2C traffic which often peaked at 25,000 requests/second. Problem Statement. Implement autoscaling of the infrastructure to handle peak traffic. Move to a Cloud-Native architecture to use modern tooling. Solve the problems related to configuration management and operational toil.

30%

Cost Saved

120

Pods at peak load

0sec

Downtime

‹ CICD

Cost-Optimization ›