Introducing Streamhouse: the open data architecture for AI | Learn More
10 AM PDT | 1 PM EDT | 10 AM BST | 10:30 AM IST | 1 PM SGT | 3 PM AEST
Facing a rapidly increasing volume of data flowing in from the various sensors and devices associated with its customers’ ever-expanding toll and smart mobility projects, ETC incorporated Kafka to address the need for scale. But as demand continued to explode, and as Kafka took on a critical infrastructure role, ETC needed to continue to scale horizontally without breaking the bank or exhausting internal resources.
Hear from ETC's Josh LittleSun, Director of Technology, on how his team charted a path to Confluent Cloud to significantly reduce the amount of time spent on managing Kafka, while reducing downtime risk and increasing agility. He explains how the introduction of Confluent enabled ETC to:
Watch now to hear the reasons why ETC switched to Confluent.