---
title: "From Always-On to On-Demand: Scaling Kafka Sinks with KED..."
url: https://daily.dev/posts/from-always-on-to-on-demand-scaling-kafka-sinks-with-ked--vltl2g6wl
source_url: https://tech.trivago.com/post/2026-02-18-from-always-on-to-on-demand-scaling-kafka-sinks-with-keda/
type: article
source: "Tech at trivago"
published: 2026-02-18T15:28:52.522Z
updated: 2026-02-18T15:29:17.326Z
tags: ["kubernetes", "architecture", "apache-kafka"]
reading_time: 16
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# From Always-On to On-Demand: Scaling Kafka Sinks with KED...

**[Tech at trivago](https://daily.dev/sources/trivago)** · 16 min read · 0 upvotes · 0 comments

## Summary

Trivago runs 50+ Kafka sink services across three regions (US, EU, ASIA) that materialize CDC events into service-local databases. Most sinks were idle the majority of the day yet consumed ~1 CPU core and 1 GB RAM each, wasting significant cluster capacity. CPU/memory-based autoscaling proved ineffective because sink workloads are I/O-bound and resource usage stays flat even when Kafka consumer lag grows. The solution was KEDA (Kubernetes Event-Driven Autoscaling) with its Kafka scaler, using consumer group lag as the scaling signal to scale deployments all the way down to zero replicas when idle. Key configuration parameters covered include `lagThreshold`, `activationLagThreshold`, `cooldownPeriod`, and `fallback`. An edge case around inactive consumer group cleanup for very low-traffic topics was solved by adding a Cron scaler to periodically wake sinks up. The rollout was gradual: one non-critical sink in one region first, then expanding after validation. Results: average daily consumption dropped from ~50 replica-hours per region to ~1–2 replica-hours.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://tech.trivago.com/post/2026-02-18-from-always-on-to-on-demand-scaling-kafka-sinks-with-keda/>

## Similar posts on daily.dev

- [KEDA: How Event-Driven Autoscaling Cuts Kubernetes Cost](https://daily.dev/posts/keda-how-event-driven-autoscaling-cuts-kubernetes-cost-dqoxqci3j) · Cast AI · 0 upvotes · 0 comments
- [How We Cut Kafka Consumer Deployment Costs by 83% · triva...](https://daily.dev/posts/how-we-cut-kafka-consumer-deployment-costs-by-83-triva--65gowghhb) · Tech at trivago · 0 upvotes · 0 comments
- [Efficient autoscaling: Keeping performance, reliability, and cost in mind with open source projects](https://daily.dev/posts/efficient-autoscaling-keeping-performance-reliability-and-cost-in-mind-with-open-source-projects-khktb08fd) · CNCF · 1 upvotes · 0 comments
- [Autoscaling AI Workloads on Kubernetes With KEDA and What it Means for Agentic Systems](https://daily.dev/posts/autoscaling-ai-workloads-on-kubernetes-with-keda-and-what-it-means-for-agentic-systems-yomfl0hvk) · Cloud Native Now · 0 upvotes · 0 comments
- [How Agoda Load Balanced Kafka](https://daily.dev/posts/how-agoda-load-balanced-kafka-vueiipyy7) · System Design Codex · 29 upvotes · 0 comments

---

Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#architecture](https://daily.dev/tags/architecture), [#apache-kafka](https://daily.dev/tags/apache-kafka)

[View this post on daily.dev](https://daily.dev/posts/from-always-on-to-on-demand-scaling-kafka-sinks-with-ked--vltl2g6wl)