Join us for NODES 2026: Engineering better intelligence | Nov 12 | Register today We are the knowledge layer that delivers accurate, explainable, and trusted AI. AI and graph technologies give agents the understanding they need to generate trustworthy outputs, and humans the understanding…
Join us for NODES 2026: Engineering better intelligence | Nov 12 | Register today We are the knowledge layer that delivers accurate, explainable, and trusted AI. AI and graph technologies give agents the understanding they need to generate trustworthy outputs, and humans the understanding…
Migrate to modernize → Modernize to unlock data → unlock data to run AI From startups to enterprises, find AWS solutions scaled to your needs. Access tailored resources, pricing models, and support levels. In this post, you learn how queue consumption mode…
The Kafka protocol is still open. The commercial center of gravity is not. Seven months after IBM closed Confluent, the questions that matter are dual-run, replay, and who owns batch when the streaming story is watsonx. Apache Kafka is still…
Get the contract wrong and no tuning fixes it. A team that picks a queue and later needs a new service to bootstrap from the last 30 days of order events has nothing to replay. A team that picks Kafka for…
This document describes the step-by-step process for upgrading an existing Kafka 2.x cluster to Kafka 3.x using a sidecar (rolling) upgrade approach — where some brokers temporarily run Kafka 2 while others run Kafka 3. This ensures no cluster downtime and enables a…
To perform a rolling upgrade from Kafka 2.8.2.3.3.6.x-x to Kafka 3.7.2.3.4.3.x-x, follow these steps: Update server.properties on All Brokers. Rolling Upgrade from Kafka 2 to Kafka 3 To perform a rolling upgrade from Kafka 2.8.2.3.3.6.x-x to Kafka 3.7.2.3.4.3.x-x, follow these steps:…
The following example is based on Kafka 3 runtime arguments and may differ for Kafka 2. Since you already have Kafka, Pinot, and Zookeeper installed, ensure they are running. It is recommended to create new topics for each service to do testing.
This topic provides steps to start a standalone Kafka cluster in ZooKeeper mode, validate its functionality, and perform a rolling upgrade from Kafka 2.8.2.3.3.6.x-x to Kafka 3.7.2.3.4.3.x-x. For details about the ODP Standalone Binaries, see Accessing Acceldata Repositories. Once all…
This document outlines the steps to perform an in-place upgrade of the Kafka cluster from Kafka 2.x to Kafka 3.x using the same data directories and ZooKeeper quorum. Before starting the upgrade, verify that the Kafka 2 cluster is fully functional.
Event streaming, pub/sub, backpressure, and consumer groups at scale.
An article joins this feed when it matches these terms. Each one is also a search of its own.