We’re excited to introduce the latest update to the **Conduit Operator**, now with built-in **schema registry support**. This new feature allows seamless data encoding and decoding, improving data compatibility across your pipelines. Whether you're managing multiple Conduit instances or scaling your data operations, schema registry integration ensures a smoother, more reliable experience for handling complex data flows.
The Conduit team has just released Conduit v0.12, and we're gearing up for the launch of Conduit v1 with a focus on making pipelines more resilient. One key feature of this release is pipeline recovery, designed to automatically restart pipelines that experience temporary errors like network interruptions or service downtime.
With configurable backoff settings, Conduit can efficiently handle retries, reducing the impact of transient issues. Learn more about this feature and how it ensures your pipelines are always up and running.
We are thrilled to introduce our latest offering, the Conduit Platform, which brings a host of new features and improvements designed to enhance your real-time data streaming experience, now powered by our robust Conduit open-source core. This transformation brings enhanced performance, scalability, and usability, coupled with access to over 100 connectors maintained by our dedicated open-source community. Here’s a closer look at what’s new and how it can benefit your data operations.
Conduit connector for Apache Flink, a powerful combination that significantly expands Flink’s capabilities. Apache Flink is renowned for its robust stream processing capabilities, while Conduit offers a lightweight and fast data streaming solution, simplifying the creation of connectors.
Explore the new features and enhancements in Conduit version 0.10, designed to streamline your data integration processes. Discover how our latest update can help improve efficiency, security, and performance for your data operations. Upgrade today and transform how you manage data with Conduit 0.10
We decided to build a performance benchmark for Conduit early, so we could determine how much it can handle and what it takes to break it.