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.
Druid Summit 2024 – Panel: Real-Time Data Experiences
Analytics applications powered by Apache Druid are fun places to be. Take a seat as user experience leaders from Google, the Data Visualisation Society, and Imply bring their minds together, and answer your...
Watch nowDruid Summit 2024 – Panel: Lakehouse Analytics
Apache Iceberg and Delta Lake are coming into the big top, and Apache Druid is ready! Get ready to hear from Apache Druid PMC members and industry experts on just where Apache Druid fits, how it can be used,...
Watch nowDruid Summit 2024 – Panel: Operations and Optimization
Come along and meet people who have implemented and tuned Druid in situations small and large – very very large! Panelists will share some of their key tips and tricks, and be open to your questions, whether...
Watch now