schema-registry
Manage evolving data and event schemas with a schema registry to ensure compatibility and safe evolution. Use when multiple producers and consumers share event or data contracts that change over time.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- schema-registry
- description
- Manage evolving data and event schemas with a schema registry to ensure compatibility and safe evolution. Use when multiple producers and consumers share event or data contracts that change over time.
03 SKILL.md 正文
Schema Registry
Overview
A schema registry stores and validates schemas (often Avro, Protobuf, or JSON Schema) so producers and consumers can evolve independently while maintaining compatibility.
When to Use
- Event-driven systems with multiple producers/consumers
- Need for enforced compatibility (backward, forward, full)
- Reducing “it works on my schema” integration bugs
Practices
- Choose a compatibility mode deliberately (backward is a common default)
- Version schemas and document changes
- Integrate schema validation into CI and runtime where appropriate
- Avoid tight coupling to a particular registry implementation in core domain logic
Principles
- Schemas are contracts — treat changes with care
- Compatibility rules should be explicit and enforced
Verification
- Incompatible schema changes are rejected automatically
- Consumers can handle the range of schemas they are expected to see
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.