From 9fb252c535c2801b7bce9b5159ab24c19d91f5c3 Mon Sep 17 00:00:00 2001
From: Soby Chacko <chackos@vmware.com>
Date: Tue, 1 Nov 2022 16:02:22 -0400
Subject: [PATCH] Schema Registry samples README enhancements

Adding instructions for how to use Confluent Schema Registry
with Spring Cloud Stream Scheam Registry AVRO converter clients.
---
 .../README.adoc                               | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/samples/spring-cloud-stream-schema-registry-integration/README.adoc b/samples/spring-cloud-stream-schema-registry-integration/README.adoc
index 8abba24c2..d410a6ed8 100644
--- a/samples/spring-cloud-stream-schema-registry-integration/README.adoc
+++ b/samples/spring-cloud-stream-schema-registry-integration/README.adoc
@@ -172,3 +172,34 @@ applied.
 
 Because each payload also includes the payload version in the header, Spring Cloud Stream with the help of Schema Registry server and Avro, the schema evolution occurs behind the scenes.
 The automatic mapping of `temperature` to `internalTemperature` field is applied, since that's the field where the `aliases` is defined.
+
+=== Using Confluent Schema Registry with Spring Cloud Stream Schema Registry AVRO Converter Clients
+
+In the examples above, we used Spring Cloud Stream Schema Registry Server with AVRO converter clients in Spring Cloud Stream.
+What if you want to use these converters, but against Confluent Schema Registry Server?
+In order to make it work, you need to provide a custom `SchemaRegistryClient` bean in your applications that knows how to interact with Confluent Schema Registry.
+
+```
+@Configuration
+static class ConfluentSchemaRegistryConfiguration {
+    @Bean
+    public SchemaRegistryClient schemaRegistryClient(@Value("${spring.cloud.stream.schema-registry-client.endpoint:http://localhost:8081}") String endpoint){
+        ConfluentSchemaRegistryClient client = new ConfluentSchemaRegistryClient();
+        client.setEndpoint(endpoint);
+        return client;
+    }
+}
+```
+
+As you can see, we are using a specific implementation of `SchemaRegistryClient` - `ConfluentSchemaRegistryClient`.
+
+You need to add this to both the producers and consumer applications.
+
+If you started Confluent Schema Registry server at a non-default server/port (`localhost:8081`), then you need to provide that using the following property.
+
+```
+spring.cloud.stream.schema-registry-client.endpoint
+```
+
+That's all there to it.
+The same applications that previously interacted with Spring Cloud Stream Schema Registry server now interacts with the Confluent Schema Registry Server using the same set of AVRO message converters provided by Spring Cloud Stream Schema Registry.