Beta Opportunity: Solace Schema Registry - Beta Now Available!
In recent years, the use of Schema Registries has been growing in order to improve data quality and governance and standardize on topics & schemas. In short, Schema Registries allow you to ensure payload compatibility between producers and consumers and upgrade schemas on different applications independently while ensuring payload compatibility.
Solace is happy to announce that the beta for Schema Registry is now live for self-managed (not PubSub+ cloud) deployment. If you would like to try the beta, the following links will help you get started:
- Codelab that will walk you through getting started with the Schema Registry Beta.
- Schema Registry Beta Package (required for the Codelab). This package has been made available to all accounts that have access to products.solace.com. If you don't have access, please reach out to your Solace account team.
This beta will roll out in stages, with new content rolling out roughly each month. Below you will see a list of our release notes. Several of the limitations listed are Day One limitations, this content will become available as the beta evolves! I will post updates as they arrive!
We welcome your feedback to help the Solace Schema Registry become the best it can be! Please reach out to your account team for any feedback or support needs.
Govern your data with quality,
Rob Tomkins
——————————————————————————————————————————— Schema Registry Beta 0.1.0 Release Notes ———————————————————————————————————————————
Schema Registry Limitations
- Delivery mechanism: Docker compose file only
- Deployment: Single instance
- Authentication: only basic auth supported
- Back-end storage: Only Postgres supported
- No administrative user support for the Schema Registry
- Not supported for production use
- Support via account teams -> PLM -> Dev only
- Supported for 1 year or until the GA of Solace Schema Registry
- Fixes to this feature will be limited to future Beta or GA releases
- Future releases of this functionality may not be backward compatible with this functionality
SERDES Limitations
- JCSMP support only (Day 1)
- Support for Avro serialization/de-serialization only (Day 1)
- No data validation (Day 1)
- No support for schema caching (Day 1)
- No support for referenced schemas (Day 1)
- No artifact resolver strategy (Day 1)
- Authentication: Only Basic Auth supported
- Minimal configuration support
- Support for Java11+ Only (Day 1)
- Not supported for production use
- Support via account teams -> PLM -> Dev only
- Supported for 1 year or until the GA of Solace Schema Registry
- Fixes to this feature will be limited to future Beta or GA releases
- Future releases of this functionality may not be backward compatible with this functionality
Comments
