Systems | Development | Analytics | API | Testing

At Confluent, our mission is to provide the world’s most secure and scalable data streaming platform. So we’re aware and planning for a future where the threat of a large-scale, cryptographically relevant quantum computer is able to break the public key cryptographic algorithms in use today. In fact, the Quantum-Safe Working Group of the Cloud Security Alliance set April 14, 2030, as the deadline by which companies should have their post-quantum infrastructure in place.

Queues for Kafka is now in General Availability (GA) on Confluent Cloud and is coming soon to Confluent Platform, coinciding with the Apache Kafka 4.2 release. This milestone brings production-ready queue semantics and elastic consumer scaling natively to Kafka through KIP-932, enabling organizations to consolidate their messaging infrastructures while gaining elastic consumer scaling and per-message processing controls. Get started.

As data architectures evolve, we are seeing a fundamental shift from systems designed to report on the past to systems designed to influence the future. At the heart of this shift are two critical, interconnected concepts: As organizations pursue more data-driven decision making, the gap between insight and action has become a competitive constraint. Together, real-time decisioning and autonomous data systems represent the evolution of real-time data systems—where insight flows directly into action.

Hey, fellow Apache Kafka developers! It’s time for another update on the Confluent client ecosystem. Following our recent architectural milestones, we’re excited to announce the release of librdkafka 2.13.0, which powers the latest versions of our Python, JavaScript, .NET, Go, and C/C++ clients. In this release, you’ll find numerous improvements to the Python experience as well as critical security and Schema Registry enhancements for everyone.

The ideal data streaming platform empowers you to handle every type of data movement with confidence. In our first Confluent Cloud launch of 2026, we’re delivering on the promise of Apache Kafka for any workload, at any scale.

While Apache Kafka is incredibly powerful, self-managing brokers, upgrades, capacity, security, and incidents can quickly distract teams from what matters most: building real-time applications and delivering business value. Confluent Cloud can remove that operational burden, yet migration can still be seen as risky and tedious.

As AI models are increasingly commoditized, the value driver for enterprises is no longer “Which large language model (LLM) are we using?” but “How can we use our data for reliable, real-time AI decisioning?” Agentic AI systems—where agents plan, decide, and act autonomously—are only as useful as the context they have. When that context is stale, fragmented, or locked away behind brittle point-to-point integrations, even the best models fail to deliver.

The road from monolithic architecture to cloud-native, microservices application is rarely a straightforward engineering exercise. There's often a significant gap between understanding the theoretical benefits of microservices and successfully extracting each service from a mature, long-running codebase. Many teams exploring microservices migration struggle most with the first extraction. How do you make that initial step concrete, low-risk, and reversible?