Why do you need a schema registry?
Enhance
Data Quality
Ensures compatibility between producers and consumers to deliver consistency of your event data across all applications, leading to more reliable business processes and analytics.
Increase Developer Productivity
Enable developers to easily discover and reuse existing schemas, generating code from schema definitions to accelerate application development and reduce errors.
Simplify
Governance
Gain central control and visibility over your event data structures, simplifying compliance and auditing efforts for distributed architectures.
What can you do with Solace Schema Registry?
Consolidate Your Schemas
Store and manage all your event schemas (Avro, JSON, XML, Protobuf, etc.) either in a single, easily accessible location,. or distributed and synchronized across environments to provide a single source of truth for your data definitions.
This gives middleware teams complete flexibility over the deployment and scope of the registry to ensure organizational needs are optimized.
Ensure Safe Schema Evolution
Implement strict versioning controls and define compatibility rules (e.g., backward, forward, full) to ensure safe schema evolution without breaking existing applications.
Protect Your Event Mesh
Schema validation continuously scans all incoming and outgoing data against registered schemas to prevent malformed messages from entering or leaving your event mesh.
How Solace Schema Registry Works
- “Governor” defines valid schema via Registry UI/API
- Publisher provides its schema subject and strategy to the registry
- If valid, registry returns schema ID
- Publisher serializer validates data and adds schema ID and schema metadata to message
- Consumer provides schema ID to registry
- Registry responds with matching schema
- Consumer de-serializer uses schema to map message metadata to variables
- Schema registries synchronize schema (optional)