linkedin

Strategic MuleSoft RTF Migration Unlocks Massive Cloud Infrastructure Cost Optimization

Impact Summary

  • 80% Idle Compute Eliminated: Successfully moved low-traffic interfaces away from rigid cloud billing models.
  • High-Density API Packing: Achieved optimal infrastructure use by packing multiple interfaces into minimal node clusters.
  • Zero Production Downtime: Completely avoided deployment risks through a structured, multi-phase environment transition.
  • Granular Resource Tuning: Enabled precise CPU and memory setup per application, breaking away from restrictive, fixed-sized blocks.

Client Overview

The client is a leading global pharmaceutical enterprise dedicated to improving patient health through innovative medical advancements and cutting-edge biotechnology.

The organization faced challenges because its existing cloud integration platform charged it a fixed price per worker regardless of actual traffic volume. This rigid setup forced the enterprise to pay premium prices for idle compute resources just to keep low-utilization APIs running. Seeking a remedy, they partnered with NJC Labs to design a modern runtime fabric strategy that could balance operational risk with infrastructure cost reduction.

The teams collaborated to implement a hybrid integration architecture, starting with development environments to validate network connectivity to core internal applications without impacting live production systems. Today, the organization enjoys a highly scalable, flexible runtime environment that automatically scales with demand, allowing it to optimize IT spend while maintaining flawless operational continuity.

Project Details

CategoryDetails
SectorPharmaceuticals & Life Sciences
Tech StackMuleSoft Anypoint Platform, CloudHub, Runtime Fabric (RTF), AWS EKS, Helm, Kubernetes, API Gateway
ApproachHybrid Integration Architecture & Phased Migration

Technical Challenges

  • Compute Inefficiency and Rigid Sizing: The enterprise relied heavily on a fully managed cloud runtime model (CloudHub). However, this model’s vCore model charges per worker regardless of actual utilization. Because nearly 80% of their vCores were serving low-traffic APIs, the business was essentially paying premium prices for idle compute.
  • Infrastructure Monoliths: The existing cloud environment lacked granular scaling. This forced the IT team to allocate entire, fixed processing blocks to simple integrations that required only a fraction of that power, leading to immense resource waste.

The Solution

1. Hybrid Deployment Model (Risk-Balanced)

NJC Labs suggested a hybrid setup to avoid an all-or-nothing migration risk:

  • Keep critical/high-SLA APIs on CloudHub: Fully managed with zero operations overhead.
  • Move low-utilization APIs to RTF: Higher density packing where you only pay for actual compute.

2. RTF for Lower Environments First

  • Immediate Cost Savings: Dev and Test environments were moved to RTF immediately, ensuring zero production risk.
  • Operational Familiarity: Teams gained RTF operational familiarity before touching production.
  • Validation: This step successfully validated Kubernetes configurations like Helm charts, resource limits, and namespace isolation.

3. Phased Production Migration

  • Phase 1: New greenfield APIs go to RTF by default.
  • Phase 2: Low-risk, low-traffic existing APIs are migrated in batches.
  • Phase 3: Evaluate remaining APIs case-by-case (some may stay on CloudHub permanently).

4. RTF on AWS EKS Specifics

  • Right-Size Resources: RTF lets you tune CPU and memory requests/limits per app, unlike CloudHub’s fixed vCore blocks.
  • Cluster Autoscaling: You only pay for nodes when load spikes.
  • Shared Routing: Shared ingress/egress via a single Anypoint MQ or API Gateway layer reduces per-app overhead.

Business Results

Cost Justification & Infrastructure Savings

RTF’s higher API density per core is the headline number. Shifting away from fixed compute blocks unlocked substantial savings:

  • Quantified Example: Where 20 APIs previously required 10 CloudHub vCores, the RTF setup serves the same load on just 3–4 nodes.
  • Quick Breakeven: Factoring in EKS node costs + RTF license vs CloudHub vCore pricing, the project breaks even quickly when utilization is low.

Operational Excellence

The engineering teams completed the EKS setup for the development environment and verified smooth connectivity to an internal application. This allowed them to safely master container isolation and automated deployments well before touching live production systems.

Looking Ahead

With a robust foundation established via this MuleSoft RTF migration, the global pharmaceutical enterprise is perfectly positioned to accelerate its digital evolution. The IT department plans to leverage this high-density containerized framework to rapidly deploy advanced analytics tools and AI-driven data pipelines. Ultimately, this scalable infrastructure ensures that the business can instantly adapt to future computational demands while keeping operational expenditures lean, predictable, and highly optimized.