I'm a member of the JSON Schema Technical Steering Committee, and been making a living consulting with companies making use of JSON Schema at large. Think data domains in the fintech industry, big OpenAPI specs, API Governance programs, etc. The tooling to support all of these use cases was terrible (non-compliant, half-baked, lack of advanced features, etc), and I've been trying to fix that. Some highlights include:
- An open-source JSON Schema CLI (https://github.com/sourcemeta/jsonschema) with lots of features for managing large schema ontologies (like a schema test runner, linter, etc)
- Blaze (https://github.com/sourcemeta/blaze), a high-performance JSON Schema C++ compiler/validator, proven to be in average at least 10x faster than others while retaining a 100% compliance score. For API Gateways and some high-throughput financial use cases
Right now I'm trying to consolidate a lot of the things I built into a "JSON Schema Registry" self-hosted micro-service that you can just provision your schemas to (from a git repo) and it will do all of the heavy lifting for you, including rich API access to do a lot of schema related operations. Still in alpha (and largely undocumented!), but working hard to transition some of the custom projects I did for various orgs to use this micro-service long term.
As a schema and open-source nerd, I'm working on my dream job :)
That's really neat. I've been doing some JSON schema work on our products recently, especially trying to take a schema and generate info compliant with the schema for e.g. testing accounts with clean data on non-production environments, etc. I feel like the area's underdeveloped.
Yeah, exactly. This is a great example. In theory schemas open up all of those use cases in an elegant manner, yet the tooling often sucks. Would love to connect and at least have your use case on my radar!
I'm a member of the JSON Schema Technical Steering Committee, and been making a living consulting with companies making use of JSON Schema at large. Think data domains in the fintech industry, big OpenAPI specs, API Governance programs, etc. The tooling to support all of these use cases was terrible (non-compliant, half-baked, lack of advanced features, etc), and I've been trying to fix that. Some highlights include:
- An open-source JSON Schema CLI (https://github.com/sourcemeta/jsonschema) with lots of features for managing large schema ontologies (like a schema test runner, linter, etc)
- Blaze (https://github.com/sourcemeta/blaze), a high-performance JSON Schema C++ compiler/validator, proven to be in average at least 10x faster than others while retaining a 100% compliance score. For API Gateways and some high-throughput financial use cases
- Learn JSON Schema (https://www.learnjsonschema.com/2020-12/), becoming the de-facto documentation site for JSON Schema. >15k visits a month
Right now I'm trying to consolidate a lot of the things I built into a "JSON Schema Registry" self-hosted micro-service that you can just provision your schemas to (from a git repo) and it will do all of the heavy lifting for you, including rich API access to do a lot of schema related operations. Still in alpha (and largely undocumented!), but working hard to transition some of the custom projects I did for various orgs to use this micro-service long term.
As a schema and open-source nerd, I'm working on my dream job :)