Imply Polaris offers Druid-as-a-Service to users with the ability to pay for ingestion only when it is used. To achieve this and keep costs down, Druid needs to scale its ingestion resources in response to customer workloads. In this session, we will talk about how we deployed Apache Druid to provide this capability to our customers first using Druid’s in built auto-scaling ingestion mechanics and then by switching to middle manager less ingestion using the druid-kubernetes-overlord extension and Kubernetes node scaling In the talk, we will discuss some of the key problems we had to solve to make deploying middle manager less ingestion a success like minimizing pod startup time and tradeoffs to consider before switching to middle manager less ingestion.
Imply Lumi: What’s New, What’s Next — and How to Unlock More Observability Value Today
Observability teams must retain more data, investigate faster, and control costs without disrupting existing tools. This live Imply Lumi update shows new ingestion, retention, search, Splunk interoperability,...
Watch nowStrategies for Managing Your Splunk Spend at Scale in 2026
Learn how a decoupled architecture for Splunk—powered by Imply Lumi and Federated Search—helps you keep more data searchable, reduce costs, and scale efficiently without changing existing Splunk workflows.
Watch nowObservability at a Breaking Point: How Decoupling Unlocks Speed, Scale, & Savings
Learn how decoupled observability helps you do more with your Splunk data, reduce costs, and scale efficiently with Federated Search.
Watch now