Tell us your queries and we’ll get back to you
Prefer email? Reach out to us at info@facets.cloud
Let us know if you have any additional queries, we'll get back to you soon.
How Vymo Leveraged Facets to Accelerate Kubernetes Migration, Enable Multi-Cloud Scalability, and Achieve 200+ Monthly Releases.
Complexity of managing multiple production environments for customers from different geographies
A lean Ops team was tasked with transformations like Kubernetes migration and optimizing Azure spend
Assumptions in application code that hindered the adoption of standard scaling strategies, leading to over-provisioning and cloud wastage
Managing more than 15 environments across multiple clouds pushing over 200 releases a month
Accelerated Kubernetes migration and well-automated infrastructure within weeks of implementation
Co-developed custom scaling strategies on top of the Platform saving 12% of cloud cost
“We have 15+ global deployments with each data center having 20+ services and we can do that pretty efficiently. We have never faced any issues with that.”
Vymo is a sales acceleration platform primarily focused on the BFSI (Banking, Financial Services, and Insurance) sector. They serve clients across multiple geographies, including India, Southeast Asia, the US, Japan, and Canada. Vymo's platform addresses critical verticals such as lending, insurance, collections, and assurance, helping organizations improve efficiency.
Vymo's multi-tenant SaaS platform also offers customizable solutions for its diverse clientele. This requires Vymo to manage multiple production environments, each with unique configurations and release requirements.
Increased complexity due to multiplicity of environments: Supporting BFSI clients meant managing custom workflows and maintaining multiple production environments across geographies. Each client often demanded unique deployment timelines and configurations, adding to operational complexity.
Drifts: Maintaining drifts across multiple regions without a centralized management solution created more work for the Ops teams.
Multi-cloud setups: While primarily on Azure, Vymo wanted cloud flexibility to honor region or customer-specific preferences. Hence, they maintained a cloud-agnostic codebase, however, taking the same approach in automation wasn’t trivial
Ops heavy Releases: As Vymo provides tailored customization for customers, release frequency and artifacts vary across environments; leading to operational overheads in releases
Limited Ops bandwidth and long roadmap: The Ops team was lean making it challenging to undertake large-scale projects like Kubernetes migration and 100% automation to manage multiple environments. The manual nature of releases and maintenance required constant intervention from the operations team, leaving little bandwidth for strategic improvements.
Poor Cloud Utilization: It was critical to manage cloud costs while scaling environments for performance and reliability, especially with the introduction of Kubernetes and new deployment strategies.
Lack of Elasticity: Vymo's infrastructure relied heavily on virtual machines (VMs) with Ansible-based configuration management. While functional, this setup lacked elasticity, scalability, and developer-centric workflows, which limited operational efficiency. Also, many services were not built keeping usual autoscaling in mind. Thus, they were over-provisioned leading to wastage. This also prevented the use of a standard spot instance management strategy without sacrificing reliability.
“When I joined Vymo, the systems were functional but rigid. Moving to Kubernetes offered the promise of elasticity and efficiency, but we needed a partner who could help us bridge the gap without disrupting our workflows”
Cost of observability: The Ops team lacked the bandwidth to fine-tune open-source solutions which increased the cost of observability infrastructure.
Drift-free multiple environments: Facets made environment management easy, self-service and enabled consistent deployment practices across multiple geographies and data centers, ensuring uniformity in configurations and releases.
Multi-cloud environments: Facets’ cloud-agnostic blueprint approach ensured that Vymo could launch multiple environments on Azure and expand to other clouds without developing additional automation. Vymo now maintains more than 15 global deployments/regions.
Centralized Configuration Management: Facets provided a centralized configuration management, which standardized environment configurations. This meant that Vymo was able to handle their multiple production environments without drifts easily.
Centralized Release Management: The centralized release management ensured that the environment-specific artifacts and frequency were centrally controlled and tracked.
Accelerating DevOps Roadmap: Facets accelerated the DevOps transformation projects
Kubernetes Migration: Vymo adopted a parallel setup, running both VMs and Kubernetes during migration. Facets supported Kubernetes-specific fine-tuning to match VM performance metrics, conducting multiple test iterations to ensure seamless performance.
The transition to Kubernetes began with lower environment operations and progressively scaled to Dev and QA environments, replacing VM-based services step-by-step.
Well-architected Observability: Developers, accustomed to tailing logs through an in-house CLI, were transitioned to Kubernetes-native live logs enriched by Facets' platform. This integration was later extended to Loki for centralized log management, simplifying workflows without disrupting productivity.
Metrics (Prometheus), and alerting (Alertmanager) accelerated the completeness of the observability stack cost-effectively.
Optimized Cloud posture: Facets and Vymo’s team collaborated to add custom scaling strategies on top of the platform to meet the application elasticity assumptions including a node labeling strategy to mix spot and on-demand instances on Azure. This resulted in 12% cloud cost savings for Vymo and strengthened product offerings on Azure.
Increased Release Frequency: Vymo performs over 200 releases per month with central tracking and management.
Cost Savings: Vymo achieved 12% cloud cost savings with migration to Kubernetes and custom scaling strategies developed over the platform
Faster Onboarding: Vymo is now able to onboard environments and get them up and running faster.
Improved Uptime: A combination of Kubernetes migration, custom scaling strategies, and proactive alerting ensured that Vymo maintained a very high availability for customers.
“No amount of testing and validation can guarantee zero downtime, but we’ve avoided many potential issues due to Facets,” says Pruthvi.
Performance Gains: Kubernetes clusters were optimized for nuanced geographies like Japan, where uptime and precision are critical. Fine-tuned configurations ensured consistent performance across multiple environments.
Vymo is looking forward to expanding support for more clouds and on-premise solutions through Facets to expand to more regions and customer segments. They aim to do this cost-optimally while minimizing distractions to the broader organization. They are also in the process of adopting the next level of process standards like blue-green deployments through Facets.
“It was the ease of adoption and the founders knew what they were doing when they started Facets. They were trying to solve a simple problem of making it easy for folks to adopt a platform-based approach. That was something that struck a chord with me initially and I have seen the positives of it.”
.png)
