Systems | Development | Analytics | API | Testing

New research with 150 Kafka practitioners reveals they have a love-and-hate relationship with the replication tools. Most use MirrorMaker2 until it lacks enterprise compliance and complexity pinches. Confluent Cluster Linking is powerful, but organisations hate being locked in. 70% of respondents would make the switch to a different tool if they were assured the migration was easy. Join Guillaume Aymé, the CEO of Lenses.io, who will be discussing the state of Kafka replication with the author of the research, Dinesh Chandrasekhar, the Founder of Stratola Research.

The standard approach for Kafka in enterprise environments is to lock it down and have engineers file tickets. Platform teams do that because traditional engineering tools (CLIs, UIs and native ACLs) have no enterprise governance, so you cannot grant access you can scope, revoke or prove later. That’s the Kafka ticket desk: the week is access requests instead of platform work, engineers wait days to ship and Kafka adoption scales only as fast as the ticket queue moves.

What's new in Q3'26: Real-time anomaly detection and forecasting with IBM Granite Time Series models and Google TimesFM model, upserts for Real-Time Context Engine to maintain fresh context for AI, and lightning queries to instantly serve the current state of the business for operational apps, analytics, and more.

Perform robust real-time forecasting on your Kafka data streams using IBM Granite Time Series models TTM, FlowState, PatchTST-FM right in Flink. Get started easily with zero-config, model flexibility, and lower cost in fully managed Confluent Cloud.

Fully managed Confluent Cloud for Apache Flink combines Flink SQL for data engineers with programmatic capabilities like the Table API, User-Defined Functions (UDFs), and Process Table Functions (PTFs) for developers. You can build mission-critical use cases with programmatic capabilities while using familiar dbt- and SQL-based workflows.