Menu

Post image 1
Post image 2
1 / 2
0

War Story: We Ditched Heroku for AWS EKS 1.32 and Saved 50% on Hosting

DEV Community·ANKUSH CHOUDHARY JOHAL·about 1 month ago
#46DEsi44
#heroku#code#story#ditched#sidecar#migration
Reading 0:00
15s threshold

In Q3 2024, our 12-person engineering team at a Series B fintech startup ripped our production workload off Heroku, migrated to AWS EKS 1.32, and cut monthly hosting spend from $42,000 to $21,000 – a 50% reduction – while dropping p99 API latency from 2.1s to 480ms and eliminating a 14-month backlog of vendor lock-in workarounds. 📡 Hacker News Top Stories Right Now Where the goblins came from (669 points) Granite 4.1: IBM's 8B Model Matching 32B MoE (10 points) Noctua releases official 3D CAD models for its cooling fans (269 points) Zed 1.0 (1875 points) The Zig project's rationale for their anti-AI contribution policy (310 points) Key Insights Monthly hosting costs dropped 50% from $42k to $21k after 6-week migration AWS EKS 1.32 with Karpenter 0.32.1 reduced node provisioning time from 4m to 12s p99 API latency improved 4.3x from 2100ms to 480ms post-migration EKS 1.32's GA sidecar support will replace 80% of third-party service mesh sidecar injection by 2025 Why We Left Heroku After 3 Years We started on…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More