Apicurio Registry vs ContractCase
Apicurio Registry
apicur.io
ContractCase
case.contract-testing.ioSide by side
| Figure | Apicurio Registry | ContractCase |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 0 | 0 |
| Spec score · Contract Testing Tools | 8.0 (#10) | 7.5 (#17) |
| Purpose | Apicurio Registry is a runtime server that stores artifacts and lets users add, update, and remove them through a remote REST API. | ContractCase is a consumer-driven contract testing framework for checking whether services can communicate as expected. |
In their own words
Apicurio Registry
Apicurio Registry is an open-source runtime server for storing API designs and schemas as artifacts. Users can add, update, and remove artifacts through a remote REST API. For API discovery, teams can register designs such as OpenAPI, AsyncAPI, and GraphQL so consumers can search and browse APIs, see details, and read generated documentation. For messaging and event streaming, it provides a central place to track schemas and manage data-format evolution. Supported artifact types include OpenAPI, AsyncAPI, GraphQL, Apache Avro, Protocol Buffers, JSON Schema, Kafka Connect schema, WSDL, XML Schema, and ODCS v3.1. Configurable rules can check validity, compatibility, and integrity as artifacts change. Listed storage backends include Apache Kafka, PostgreSQL, and Microsoft SQL Server. Management options include a web console, REST API, command line, Maven plug-in, and Java client. Kafka serializers and deserializers can enforce schemas in producer and consumer applications. The documentation covers self-hosted deployment, including Kubernetes. The quick-start in-memory server is non-persistent and is not intended for production.
ContractCase
ContractCase has no write-up on Specifiction yet; its figures are above.