If you've ever visualized a Kafka cluster with Schema Registry, you've probably seen the problem: a single Avro/Protobuf/JSON schema registered under multiple subjects (e.g., orders-value, payments-value, returns-value) creates separate nodes that are all structurally identical. In a cluster with dozens of topics, the graph becomes unreadable.
If you've ever visualized a Kafka cluster with Schema Registry, you've probably seen the problem: a single Avro/Protobuf/JSON schema registered under multiple subjects (e.g., orders-value, payments-value, returns-value) creates separate nodes that are all structurally identical. In a cluster with dozens of topics, the graph becomes unreadable.
Full demo : https://www.youtube.com/watch?v=lQIdaqVqgtk
Does streamlens only looks for subject naming strategy config as default for schemas?
Yes, based on that, subject-value, key are derived.