[Webinar] Build Your GenAI Stack with Confluent and AWS | Register Now
Confluent Hub launched in 2018 as a place to discover and share Apache Kafka® and Confluent Platform plugins. Users have found the site a much better place to discover useful code than seeking out individual git repos. These plugins include connectors, Single Message Transforms (SMTs), and converters for Kafka Connect. At launch, we had a humble inventory of about a dozen plugins. Now, there are over 140 available, including 100+ that are fully supported by Confluent and our partners!
Since its launch, we’ve looked for ways to improve Confluent Hub, and today we’re happy to introduce a complete frontend redesign, based on user feedback. In particular, we’ve tried to make it much easier to parse plugins across dimensions that matter most to developers.
The most notable update to Confluent Hub is the addition of a detailed plugin taxonomy that lets you filter options across a number of key plugin dimensions.
Determining the plugin type you need is likely your first concern as a developer. The plugin types on Confluent Hub are as follows:
Depending on where you’re doing your development, you may or may not need access to enterprise-level support. You might even be quite adventurous with your own projects. Lots of companies we talk to, however, aren’t comfortable putting something into production without the ability to get expert support on the phone. To help both types of users navigate the available plugins, Confluent Hub lets you filter by enterprise support type:
Similar to enterprise support, you may or may not be developing in an environment that requires everything to be ready for “enterprise scale” from day zero. It’s impossible to point to a single benchmark that quantifies this, but these verification levels are our attempt to identify at least those plugins that are known to be built for high performance and stability. These categories include:
This one is pretty straightforward:
Our fully managed Apache Kafka as a service product, Confluent Cloud, offers some of these connectors, fully managed, on leading public clouds like Google Cloud Platform (GCP), Microsoft Azure, and Amazon Web Services (AWS).
That’s a quick overview of what’s changed in the Confluent Hub frontend. We’re always looking for ways to improve the product and serve the community better, and one of the key ways we do this is by adding new open source and partner connectors to Confluent Hub. If you would like to get your code in front of more developers, or if you’d just like to give some feedback, send us an email at confluent-hub@confluent.io. We look forward to hearing from you!
We covered so much at Current 2024, from the 138 breakout sessions, lightning talks, and meetups on the expo floor to what happened on the main stage. If you heard any snippets or saw quotes from the Day 2 keynote, then you already know what I told the room: We are all data streaming engineers now.
We’re excited to announce Early Access for Confluent for VS Code. This Visual Studio integration streamlines workflows, accelerates development, and enhances real-time data processing, all in a unified environment. This post shows how to get started, and also lists opportunities to get involved.