Success Story
n1co migrates its microservices from Azure to AWS in 5 months, on time and with no incidents
At a glance
n1co is a Central American fintech founded in April 2022. Its Azure infrastructure was expensive, hard to scale and limited for running critical microservices. Craftech migrated its microservices to a scalable AWS infrastructure based on Amazon EKS. The migration was completed in 5 months, on time and with no incidents during execution.
5 months
from Azure to AWS, on time
n1co is a Central American fintech founded in April 2022 with the mission of evolving the region's financial system and building an inclusive, trustworthy ecosystem.
Solution implemented
- Scalable AWS infrastructure based on Amazon EKS, with development and production clusters
- Components to standardize deployments: ArgoCD, CI/CD, Grafana and Prometheus
- Database migration with SQLPackage, chosen after testing several tools
- Hybrid approach with an NLB as a proxy to RDS for public-access cases
- Lower-environment databases consolidated into a single instance to reduce costs
- Azure Service Bus kept in the lowest-latency region, since replacing it required code changes
Business Challenge
n1co's Azure infrastructure was expensive, hard to scale and limited for running critical microservices. The migration posed two concrete problems: choosing the right tool to migrate the databases while ensuring continuity, with a higher cost on AWS due to licensing, and solving external dependencies, such as Azure Service Bus, that had no equivalent design on AWS. A first attempt with Azure SQL Data Sync took a very long time and ran into issues with indexes and formats.
Solution
Craftech built a scalable AWS infrastructure based on Amazon EKS, with development and production clusters and components to standardize deployments: ArgoCD, CI/CD, Grafana and Prometheus. For the databases it chose SQLPackage after testing several tools, with a hybrid approach for public-access cases: an NLB acting as a proxy to RDS. Lower-environment databases were consolidated into a single instance to reduce costs. Azure Service Bus was kept in the lowest-latency region, since replacing it required code changes.
Outcomes
- Successful migration to AWS, on time and with no incidents during execution
- Better CI/CD observability and Kubernetes resource versioning with GitOps and ArgoCD
- Simplified access with VPN, Leapp and AWS IAM Identity Center integrated with Okta
- More scalable infrastructure, with long-term log retention (Loki) and centralized metrics (Thanos)
- Modernized stack with AWS Control Tower, ArgoCD and Terraform, and lower costs in lower environments
Stack & technologies
