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.

Fivetran vs Talend in 2026: Which ETL Tool Is Better? Fivetran and Talend follow different approaches to data integration. Fivetran focuses on managed, warehouse-first ELT with automatic connector maintenance and schema handling. Talend supports ETL, ELT, data quality, governance, APIs and hybrid deployment across cloud and on-premises environments.

Learn how to build an end-to-end, real-time edge-to-AI data pipeline to tackle critical enterprise challenges like credit card fraud detection. In this demo, Diby Malakar (Product Lead for Data in Motion) demonstrates how to process an average of 5,000 transactions per second in low hundreds of milliseconds to detect fraud instantly. Discover how Cloudera’s Data in Motion suite enables application developers to ingest, govern, and enrich streaming edge data to power instant AI model inference and live analytics.

Stop burning budgets on AI for AI's sake. With billions pouring into data centers, many enterprises are experiencing massive buyer's remorse. How do you ensure your company is part of the 10% actually driving results? Guest Mark Ritcey breaks down.

If an AI agent gives a business user the wrong number, and a consequential decision gets made off it, who's responsible? The data analyst who built the semantic layer? The platform? Or the business user who asked the question and acted on the answer?