Ross ROSS = Recommend OSS · open-source software intelligence for agents

confluentinc/schema-registry

Confluent Schema Registry for Kafka observed · 2026-08-28

github.com/confluentinc/schema-registry · homepage · Java · NOASSERTION (other) observed · 2026-08-28

Health v2 · maintenance only

77/100

  • Activity 99
  • Release rhythm 35
  • Longevity 100

Flags: no_releases no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 4285
  • days_rel: n/a
  • days_push: 7
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

2462 stars · 1159 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Confluent Schema Registry is a Java-based serving layer that stores and retrieves Avro, JSON Schema, and Protobuf schemas via a RESTful API, maintaining versioned schema history with configurable compatibility rules. It integrates with Apache Kafka clients through serializers/deserializers that handle schema storage and retrieval for message data.

Use cases

  • manage and version avro schemas for kafka topics
  • enforce schema compatibility rules when evolving event data
  • serialize and deserialize kafka messages with avro, protobuf, or schemas
  • store protobuf and schemas centrally for streaming pipelines
  • validate producer and consumer schema compatibility in kafka
  • expose a rest api for schema registration and lookup
  • implement data governance and data contracts for kafka streams

When to choose

  • you use Apache Kafka and need centralized schema management with compatibility enforcement
  • your producers and consumers need Avro, Protobuf, or JSON Schema serialization wired into Kafka clients
  • you require versioned schema history and safe schema evolution for event streaming pipelines
  • you want a self-hosted or Confluent Cloud schema repository with a REST API

When to avoid

  • you don't use Kafka or a compatible event streaming platform
  • you only need lightweight schema validation without a centralized registry service
  • you need a schema store for non-streaming use cases like database migrations
  • you cannot operate a JVM-based service and don't want a managed cloud option

Facets

service · maturity active

serialization api-framework http-server database apis big-data developer-tools jvm self-hosted kafka schema-registry avro protobuf -schema schema-evolution data-governance rest-api confluent data-engineering streaming docker kubernetes web-server

10 sources

Member repositories

RepositoryRoleHealth v2
confluentinc/schema-registrymain77

For agents

markdown · JSON · MCP: product_card(name="confluentinc/schema-registry")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem