Apicurio Registry is most often used as the schema registry for Apache Kafka. These posts cover the client serializers and deserializers, Kafka Connect, schema references, and storing the registry itself in Kafka.
If you run Debezium or any other Kafka Connect pipeline on Protobuf, you have had to make a choice: give up on Protobuf and fall back to Avro, or give up on Apicurio Registry’s native API and route Confluent’s converter...
Apicurio Registry allows to manage artifacts with references as shown in the documentation. One of the cool features we’ve added on top of this is the possibility of using a dereference parameter for certain API endpoints that optionally allows you...
Serialization and deserialization (SerDes) are critical functionalities within Apicurio Registry, enabling users to seamlessly manage schema evolution and compatibility. With the release of Apicurio Registry 3.x, we’ve significantly evolved our SerDes modules, focusing on flexibility, reusability, and broader integration.
As promised in the announcement blog about the upcoming release of Apicurio Registry 3.0, this post is a deep dive into the changes we’re making to our Kafka storage variant. We’ll get into what the KafkaSQL storage variant is and...
KafkaSQL is a popular storage option for Apicurio Registry, introduced in version 2.0.0.Final. It has become very reliable, despite its higher complexity compared to the SQL storage option. Sadly, no software is immune to bugs, and KafkaSQL is no exception....
Reference documentation: Validating Kafka messages using SerDes.
Other topics: Securing Apicurio Registry · Migrating to Apicurio Registry 3.x · AI agents, MCP and LLM artifacts ·