Teams are being asked to retain more data, investigate problems and incidents further back in time, and respond faster — all while controlling costs. The challenge isn't a lack of tools; it's the tightly coupled architectures.
In this session, we'll explore why decoupling the data layer from the interaction layer is critical. Using a real-world use case, we'll see how traditional approaches force teams to trade off visibility, performance, or usability at the worst possible moment.
We'll break down how a decoupled architecture allows teams to run continuous detections on recent data while elastically scaling across large historical datasets, without duplicating data or abandoning existing workflows.
The result is greater flexibility, better cost control, and faster incident response — even as data volumes and retention requirements continue to grow.
Peter Marshall is a technology leader and community builder with a background in developer relations, data architecture, and digital transformation. As Director of Developer Relations at Imply, he leads programs that grow and engage the global Apache Druid community through education, support, and events. With experience across startups, enterprises, and the public sector, Peter brings a blend of technical expertise and strategic vision to help organizations connect with developers and drive impact through open source.
