As the amount of data in Fintech and cryptocurrency applications has increased, Kafka has become the norm for wrangling this surge at speed and scale. However, the need to send personalized data streams to users has become paramount. Your mobile day trader only wants what they can use, and neither you nor they want the data bill for everything they are not using. You also don’t want topics per user. This is where it started, but as we’ve encountered more Kafka users, the needs are increasingly similar - whether it's large-scale chat systems, betting applications, or social media. Data access patterns are not but all need to be handled fairly. In this session, I’ll walk you through designing a scaling consumer system to allow for customized user streams in high cardinality data topics, all while minimizing the data burden on user devices. I’ll be demonstrating a few use cases of the system and running through the various tradeoffs that can be made to both improve user latency and add high availability to the system. Follow along to learn about the key tradeoff of user experience vs cost, latency vs flexibility, and the increasing demands of user-facing systems.
Roman de Oliviera
Solutions Engineer @Ably
Roman is a Solutions Engineer at Ably where he helps customers realize the benefits of infrastructure that powers realtime digital experiences and creates solutions unique to the customers' challenges. Prior to Ably, Roman worked at MuleSoft as Lead Solution Engineer.