Summary Apicurio Registry is an API and Schema registry designed to store, manage, and version APIs and their schemas. It targets developers and organizations needing a centralized solution for API governance, discovery, and integration throughout the API lifecycle.

How It Works Built on Quarkus, this Java application offers pluggable persistence, supporting In-Memory, KafkaSQL, PostgreSQL, and community-contributed SQL Server. Runtime configuration via command-line arguments or environment variables selects the storage backend. A three-tier build system (Fast, Default, Full) allows users to compile only necessary components, optimizing build times and artifact size for development or CI/release workflows. It also integrates with OpenID Connect (OIDC) for centralized authentication and authorization.

Quick Start & Requirements

• Primary Install/Run:
  • Build: ./mvnw clean install (use -Dfast, -Dfull for build tiers).
  • Dev Server: ./mvnw quarkus:dev (API docs on localhost:8080).
  • UI Dev: cd ui, npm install, cd ui-app, ./init-dev.sh, npm run dev (UI on localhost:8888).
  • Docker: docker run -p 8080:8080 apicurio/apicurio-registry:latest-snapshot (and apicurio/apicurio-registry-ui:latest-snapshot for UI).
• Prerequisites: JDK, Maven, Node.js (for UI), Docker. Specific persistence backends may require running PostgreSQL, SQL Server, or Kafka instances.
• Links: API documentation and User Interface are accessible locally after startup.

Maintenance & Community The README does not detail specific contributors, sponsorships, or community channels (e.g., Discord, Slack).

Licensing & Compatibility The README does not explicitly state the project's license, requiring further investigation for commercial use or closed-source linking compatibility.

Limitations & Caveats SQL Server persistence is community-contributed. Eclipse IDE users may need specific configurations for Lombok and maven-dependency-plugin. The project's license is not explicitly stated.