See how we optimized our multi-AZ Kubernetes clusters by solving two long-standing inefficiencies: static pod resources & costly cross-AZ traffic

HaloDoc is a healthcare technology platform that offers telemedicine services, online pharmacy, and health information resources to users in Indonesia. Through its platform, HaloDoc aims to improve access to healthcare services, empower patients to take control of their health, and facilitate collaboration between healthcare providers. Developers can learn from HaloDoc's innovative use of technology to address healthcare challenges, leveraging telemedicine, artificial intelligence, and data analytics to enhance patient care and outcomes.

Halodoc

Halodoc reduced Kubernetes infrastructure costs by implementing two optimization strategies: in-place pod resizing to dynamically adjust resources during low-traffic periods without restarts (achieving ~15% CPU and ~10% memory reduction), and zone-aware routing to minimize cross-AZ traffic (reducing data transfer costs by ~25% and latency by ~5%). The approach uses a custom scheduler for periodic resource patching and Kubernetes' trafficDistribution: PreferClose feature combined with topology spread constraints to keep traffic within availability zones.

Kubernetes OptimizationInPlace Pod Resizing,ZoneAware Routin

The Non-Business Hours Under-Utilization Problem

Enter In-Place Pod Resizing: Right-Sizing Without Restart

Zone-Aware Routing: Traffic Within the Zone