Confluent 模式注册表与 Spring 云模式注册表 [英] Confluent schema registry vs Spring cloud schema registry

问题描述

我目前一直在研究 Spring Cloud 模式注册表和融合模式注册表.我可以看到一些差异，例如 spring 云模式注册表将模式保存在普通数据库中，默认情况下保存在 h2 中，而融合模式注册表保存在 kafka 主题中.

I have been looking at spring cloud schema registry and confluent schema registry for now. I could see a few difference such as spring cloud schema registry saves schemas in normal database and by default in h2 whereas confluent schema registry is saved in kafka topic.

对于 Spring Cloud 模式注册表，这种方法是否有任何性能影响.据我所知，即使数据在融合的情况下保持在主题上，查询它仍然会延迟.但会产生重大影响吗?

Is there any performance impact to this approach for spring cloud schema registry. As far as I understood even though the data is kept on topic in case of confluent there would still be a delay in querying it. But would there be a major impact?

我还看到spring cloud schema registry提供了对confluent schema registry的支持，这是否意味着confluent schema registry更好?

Also I could see that spring cloud schema registry provides support for confluent schema registry, does that mean confluent schema registry is better?

这些模式注册表的工作方式有什么根本区别吗?

Is there any fundamental difference in working of these schema registries?

如果融合架构注册表已经可用，那么还需要什么 Spring Cloud 架构注册表?

What is the need for spring cloud schema registry if the confluent schema registry was already available?

推荐答案

从 Spring Cloud Stream Kafka 的角度，推荐使用 Confluent Schema Registry.将 Spring Cloud Stream 与 Confluent Schema Registry 集成起来相当容易.有一些可用的示例这里 证明了这一点.Spring Cloud Schema Registry 是一个处于维护模式的项目，我们可能不会向其添加任何进一步的功能.如果您使用的是 Kafka，那么使用 Spring Cloud Schema 注册表并没有太大的优势.如果您针对 RabbitMQ、AWS Kinesis 等非 Kafka 中间件系统执行架构演化，Spring Cloud Schema 注册表可能会变得有用.正如您所指出的，默认情况下它使用 H2 数据库，您可以为其他数据库配置它.如果您发现 Spring Cloud Stream 和 Confluent Schema Registry 之间的集成有任何问题，请在 Kafka Binder 中提出它们 GH 存储库.

From a Spring Cloud Stream Kafka perspective, it is recommended to use the Confluent Schema Registry. It is fairly easy to integrate Spring Cloud Stream with Confluent Schema Registry. There are a few samples available here demonstrating that. Spring Cloud Schema Registry is a project that is in maintenance mode and we may not add any further features to it. There is not much advantage of using Spring Cloud Schema registry if you are using Kafka. Spring Cloud Schema registry may become useful if you are performing schema evolution against a non-Kafka middleware system such as RabbitMQ, AWS Kinesis, etc. As you noted, by default it uses the H2 database and you can configure it for other databases. If you find any issues with the integration between Spring Cloud Stream and Confluent Schema Registry, please raise them in the Kafka Binder GH repository.

这篇关于Confluent 模式注册表与 Spring 云模式注册表的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！