Systems | Development | Analytics | API | Testing

Confluent's Customer Zero: Supercharge Lead Scoring with Apache Flink and Google Cloud Vertex AI, Part 1

At Confluent, we continuously strive to showcase the power of our data streaming platform through real-world applications, exemplified by our Customer Zero initiative. In part 1 of this blog, we present the latest use case of Customer Zero that harnesses the capabilities of generative AI, data streaming, and real-time predictions to enhance lead scoring for sales, helping our team prioritize high-value prospects and address complex challenges within our organization.

Are You Misconfiguring Producer Retries? | Kafka Developer Mistakes

Producer retries in Apache Kafka can make or break message delivery, especially during broker events like updates or failures. Use the idempotent producer, and configure delivery timeouts, in order to avoid common pitfalls that lead to lost messages or broken ordering.

Unify Streaming and Analytical Data with Apache Iceberg, Confluent Tableflow, and Amazon SageMaker Lakehouse

Earlier this year, we unveiled our vision for Tableflow to feed Apache Kafka streaming data into data lakes, warehouses, or analytical engines with a single click. Since then, many customers have been exploring, experimenting with, and providing valuable feedback on Tableflow Early Access. Our teams have worked tirelessly to incorporate this feedback and are excited to bring Tableflow Open Preview to you in the near future.

Are You Using the Wrong Partition Key? | Kafka Developer Mistakes

Picking the wrong partition key in Apache Kafka? That’s a fast track to performance headaches—think unbalanced loads, slowdowns, and broken message ordering. Choosing the right partitioning strategy keeps your data flowing smoothly and avoids hot partitions.

Why Short-Lived Connections Are Killing Your Performance! | Kafka Developer Mistakes

Constantly starting and stopping Apache Kafka producers and consumers? That’s a recipe for high resource usage and inefficiency. Short-lived connections are heavy on resources, and can slow down your whole cluster. Keep them running to boost performance, cut latency, and get the most out of your Kafka setup.

Securely Query Confluent Cloud from Amazon Redshift with mTLS

Querying databases comes with costs—wall clock time, CPU usage, memory consumption, and potentially actual dollars. As your application scales, optimizing these costs becomes crucial. Materialized views offer a powerful solution by creating a pre-computed, optimized data representation. Imagine a retail scenario with separate customer and product tables. Typically, retrieving product details for a customer's purchase requires cross-referencing both tables.

Why Relying on Default Settings Can Cost You! | Kafka Developer Mistakes

Default settings in Apache Kafka work when you’re getting started, but aren't suited for production. Sticking with defaults, like a seven-day retention policy, or a replication factor of one, can cause storage issues, or data loss in case of failure. Learn why optimizing retention periods, replication factors, and partitions, is crucial for better Kafka performance and reliability.

Confluent Introduces Enterprise Data Streaming to MongoDB's AI Applications Program (MAAP)

Today, Confluent, the data streaming pioneer, is excited to announce its entrance into MongoDB’s new AI Applications Program (MAAP). MAAP is designed to help organizations rapidly build and deploy modern generative AI (GenAI) applications at enterprise scale.

Why Using Outdated Versions Hurts Your System! | Kafka Client Mistakes

Keeping your Apache Kafka clients up-to-date is critical for maximizing performance, security, and stability. In this video, we discuss why sticking with old versions could be putting you at risk, since it means you’re missing out on dozens of new features, and hundreds of bug fixes and security patches. Learn why upgrading is more than just a “nice-to-have”—it’s essential for a smoother and safer Kafka experience.

Deep Dive into Handling Consumer Fetch Requests: Kafka Producer and Consumer Internals, Part 4

Recap: This is the last part of our four chapters: It’s been a long time coming, but we’ve finally arrived at the fourth and final installment of our blog series. In this series, we’ve been peeling back the layers of Apache Kafka to get a deeper understanding of how best to interact with the cluster using producer and consumer clients. At a high level, a fetch request is comprised of two parts: Let’s dive in.