Services

Resources

Company

Our Work

Blog

Check out our best work

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

Learn More

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

Learn More

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

Learn More

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

Learn More

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

Learn More

AutoScaling eKYC Machine Learning workloads to 2M+ req/day

Cloud monthly costs were reduced to a maximum of $10k per month (90% savings over predicted costs without the Autoscaler). The solution has been live and running successfully on production for 2+ years. SLA for uptime and response time are met during this period.

Learn More

AutoScaling eKYC Machine Learning workloads to 2M+ req/day

Cloud monthly costs were reduced to a maximum of $10k per month (90% savings over predicted costs without the Autoscaler). The solution has been live and running successfully on production for 2+ years. SLA for uptime and response time are met during this period.

Learn More

AutoScaling eKYC Machine Learning workloads to 2M+ req/day

Cloud monthly costs were reduced to a maximum of $10k per month (90% savings over predicted costs without the Autoscaler). The solution has been live and running successfully on production for 2+ years. SLA for uptime and response time are met during this period.

Learn More

AutoScaling eKYC Machine Learning workloads to 2M+ req/day

Cloud monthly costs were reduced to a maximum of $10k per month (90% savings over predicted costs without the Autoscaler). The solution has been live and running successfully on production for 2+ years. SLA for uptime and response time are met during this period.

Learn More

AutoScaling eKYC Machine Learning workloads to 2M+ req/day

Cloud monthly costs were reduced to a maximum of $10k per month (90% savings over predicted costs without the Autoscaler). The solution has been live and running successfully on production for 2+ years. SLA for uptime and response time are met during this period.

Learn More

How we saved more than 42% on AWS Infrastructure Costs

The client a no-code platform to build mobile apps for a Shopify store. The platform is hosted on AWS and serves customers across the globe. Operational for 7+ years and have a 30+ member dev team with not much DevOps expertise in the team. Problem Statement. Reduce existing cloud infrastructure cost of $25k/month without affecting the business metrics and uptime. Implement cloud governance and infrastructure access policies for security. Continuous billing monitoring, alerts and deeper insights into cost allocations..

42%

Cost reduction for AWS Compute service

56%

Cost reduction for AWS RDS

90%

Cost reduction for AWS Data transfer

Learn More

How we saved more than 42% on AWS Infrastructure Costs

The client a no-code platform to build mobile apps for a Shopify store. The platform is hosted on AWS and serves customers across the globe. Operational for 7+ years and have a 30+ member dev team with not much DevOps expertise in the team. Problem Statement. Reduce existing cloud infrastructure cost of $25k/month without affecting the business metrics and uptime. Implement cloud governance and infrastructure access policies for security. Continuous billing monitoring, alerts and deeper insights into cost allocations..

42%

Cost reduction for AWS Compute service

56%

Cost reduction for AWS RDS

90%

Cost reduction for AWS Data transfer

Learn More

How we saved more than 42% on AWS Infrastructure Costs

The client a no-code platform to build mobile apps for a Shopify store. The platform is hosted on AWS and serves customers across the globe. Operational for 7+ years and have a 30+ member dev team with not much DevOps expertise in the team. Problem Statement. Reduce existing cloud infrastructure cost of $25k/month without affecting the business metrics and uptime. Implement cloud governance and infrastructure access policies for security. Continuous billing monitoring, alerts and deeper insights into cost allocations..

42%

Cost reduction for AWS Compute service

56%

Cost reduction for AWS RDS

90%

Cost reduction for AWS Data transfer

Learn More

How we saved more than 42% on AWS Infrastructure Costs

The client a no-code platform to build mobile apps for a Shopify store. The platform is hosted on AWS and serves customers across the globe. Operational for 7+ years and have a 30+ member dev team with not much DevOps expertise in the team. Problem Statement. Reduce existing cloud infrastructure cost of $25k/month without affecting the business metrics and uptime. Implement cloud governance and infrastructure access policies for security. Continuous billing monitoring, alerts and deeper insights into cost allocations..

42%

Cost reduction for AWS Compute service

56%

Cost reduction for AWS RDS

90%

Cost reduction for AWS Data transfer

Learn More

How we saved more than 42% on AWS Infrastructure Costs

The client a no-code platform to build mobile apps for a Shopify store. The platform is hosted on AWS and serves customers across the globe. Operational for 7+ years and have a 30+ member dev team with not much DevOps expertise in the team. Problem Statement. Reduce existing cloud infrastructure cost of $25k/month without affecting the business metrics and uptime. Implement cloud governance and infrastructure access policies for security. Continuous billing monitoring, alerts and deeper insights into cost allocations..

42%

Cost reduction for AWS Compute service

56%

Cost reduction for AWS RDS

90%

Cost reduction for AWS Data transfer

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

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

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

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

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

Learn More

Pull Request Based Ephemeral Preview Environments on Kubernetes

Problem Statement. Set up Heroku PaaS style, ephemeral Preview environments for all frontend and backend services on Kubernetes Allow a Preview service to use another service in Preview mode as a dependency Configure the latest migrations and seed data in Preview environments, reducing the time to test a Pull Request Allow automated deletion of the Preview environment if it’s not actively used

Learn More

Pull Request Based Ephemeral Preview Environments on Kubernetes

Problem Statement. Set up Heroku PaaS style, ephemeral Preview environments for all frontend and backend services on Kubernetes Allow a Preview service to use another service in Preview mode as a dependency Configure the latest migrations and seed data in Preview environments, reducing the time to test a Pull Request Allow automated deletion of the Preview environment if it’s not actively used

Learn More

Pull Request Based Ephemeral Preview Environments on Kubernetes

Problem Statement. Set up Heroku PaaS style, ephemeral Preview environments for all frontend and backend services on Kubernetes Allow a Preview service to use another service in Preview mode as a dependency Configure the latest migrations and seed data in Preview environments, reducing the time to test a Pull Request Allow automated deletion of the Preview environment if it’s not actively used

Learn More

Pull Request Based Ephemeral Preview Environments on Kubernetes

Problem Statement. Set up Heroku PaaS style, ephemeral Preview environments for all frontend and backend services on Kubernetes Allow a Preview service to use another service in Preview mode as a dependency Configure the latest migrations and seed data in Preview environments, reducing the time to test a Pull Request Allow automated deletion of the Preview environment if it’s not actively used

Learn More

Pull Request Based Ephemeral Preview Environments on Kubernetes

Problem Statement. Set up Heroku PaaS style, ephemeral Preview environments for all frontend and backend services on Kubernetes Allow a Preview service to use another service in Preview mode as a dependency Configure the latest migrations and seed data in Preview environments, reducing the time to test a Pull Request Allow automated deletion of the Preview environment if it’s not actively used

Learn More

Backup and recovery solution for SIEM data at Terabyte scale

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

1.5TB

Dataset handeled daily

100+

tenents using backup restore solution

$200

Running cost per month

Learn More

Backup and recovery solution for SIEM data at Terabyte scale

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

1.5TB

Dataset handeled daily

100+

tenents using backup restore solution

$200

Running cost per month

Learn More

Backup and recovery solution for SIEM data at Terabyte scale

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

1.5TB

Dataset handeled daily

100+

tenents using backup restore solution

$200

Running cost per month

Learn More

Backup and recovery solution for SIEM data at Terabyte scale

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

1.5TB

Dataset handeled daily

100+

tenents using backup restore solution

$200

Running cost per month

Learn More

Backup and recovery solution for SIEM data at Terabyte scale

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

1.5TB

Dataset handeled daily

100+

tenents using backup restore solution

$200

Running cost per month

Learn More

Homogeneous Monitoring across Cloud and On-premise

Monitor CPU, Memory, and Disk Utilization of the host systems and application containers. We needed a uniform solution to fetch metrics across AWS, GCP and on-premise data centers. All metrics should be stored and served from a single storage backend for uniformity, visualization and alerting.

Learn More

Homogeneous Monitoring across Cloud and On-premise

Monitor CPU, Memory, and Disk Utilization of the host systems and application containers. We needed a uniform solution to fetch metrics across AWS, GCP and on-premise data centers. All metrics should be stored and served from a single storage backend for uniformity, visualization and alerting.

Learn More

Homogeneous Monitoring across Cloud and On-premise

Monitor CPU, Memory, and Disk Utilization of the host systems and application containers. We needed a uniform solution to fetch metrics across AWS, GCP and on-premise data centers. All metrics should be stored and served from a single storage backend for uniformity, visualization and alerting.

Learn More

Homogeneous Monitoring across Cloud and On-premise

Monitor CPU, Memory, and Disk Utilization of the host systems and application containers. We needed a uniform solution to fetch metrics across AWS, GCP and on-premise data centers. All metrics should be stored and served from a single storage backend for uniformity, visualization and alerting.

Learn More

Homogeneous Monitoring across Cloud and On-premise

Monitor CPU, Memory, and Disk Utilization of the host systems and application containers. We needed a uniform solution to fetch metrics across AWS, GCP and on-premise data centers. All metrics should be stored and served from a single storage backend for uniformity, visualization and alerting.

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

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

Learn More

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

Learn More

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

Learn More

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

Learn More

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

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

Checkout our latest posts.

June 18, 2025 | 5 min read

Implementing Secure Error Handling in Go for B2B SaaS applications

Mohit Kumar

Software Engineer

A centralized error handling library helped our team improve user experience and strengthen security in Go-based microservices by replacing leaky, inconsistent error messages with structured, user-friendly responses.

June 4, 2025 | 5 min read

Deploying a scalable NATS Cluster Part 1: Core Architecture and Considerations

Barun Debnath

SRE @One2N

In this blog, we provide a detailed overview of the NATS architecture, key cluster design considerations, and best practices for deploying a scalable and reliable NATS messaging system. We cover topics like high availability, fault tolerance, message durability, and the infrastructure requirements.

May 14, 2025 | 8 min read

Optimizing MongoDB backup strategy: Lessons from achieving a 1-Hour RPO

Mihir Bhagwat

SRE @One2N

Sanket Rajgiri

SRE @One2N

This post walks through how we implemented a disaster recovery solution for a MongoDB cluster running on Google Kubernetes Engine (GKE) using the MongoDB Community Operator

April 29, 2025 | 9 min read

Transforming Alerting with GitOps - A Journey in Automating Elasticsearch Alerts

Srivatsa RV

SRE @One2N

This blog tells you how to approach alerting from first principles while on the ELK Stack. We cover how to capture the right signals that a NOC team looks at, structure them as alert definitions and operationalize them relying on GitOps. This ensures teams can act on alerts confidently.

April 10, 2025 | 5 min read

GitHub Runners Fundamentals and Self-Hosted Runner Setup

Rajesh Jangid

SRE

This post is an introduction to Github runners, different ways in which they can be deployed, and a comparison between managed and self hosted runners.

April 8, 2025 | 4 min read

All software is assembled

Chinmay Naik

Founder, CEO @One2N

Learn why modern software development relies more on strategic assembly of third-party components over building them from scratch.

Blog