TechPrufer
Sign inGet started

Blogs›Confluent›Real-time Edge Messaging Integration

Real-time Edge Messaging Integration

Real-time Edge Messaging Integration

2
posts
2019–2022

This release enhances Confluent Cloud's capabilities for building real-time, high-throughput UIs that visualize Kafka message streams. It details the evolution from traditional pagination and long polling to WebSockets and then Web Workers to achieve performant message consumption and rendering in a browser. The post highlights the challenges of UI responsiveness with high message throughput and the technical solutions implemented to overcome them, including optimizing state management (Redux to React components) and offloading processing to web workers.

2022

Building a Real-Time Betting Platform with Confluent Cloud and Ably

4/4/2022

This post details the architecture and implementation of a real-time betting platform by combining Confluent Cloud with Ably. It highlights the use of the Ably Kafka Connector for bidirectional data flow between Confluent Cloud topics and Ably. The architecture involves using Confluent Cloud for backend event streaming and processing (including ksqlDB for materialized views and odds generation), and Ably for distributing real-time odds and notifications to end-users via WebSockets, as well as collecting bets from users back into Confluent Cloud. The post emphasizes the benefits of this integration, including low latency, scalability, reliability, data integrity, and ease of use.

2019

Consuming Messages Out of Apache Kafka in a Browser | Confluent

3/28/2019

This post details the technical challenges and solutions for building a performant UI to visualize high-throughput Kafka message streams in a web browser. It explores the limitations of pagination and long polling, the benefits and initial performance issues of WebSockets, and the eventual adoption of Web Workers to offload processing and maintain UI responsiveness. The post also discusses optimizations made to state management (moving from Redux to React components) and the use of batching within web workers to further improve throughput.