Amazon EventBridge vs Apicurio Registry

Amazon EventBridge is a serverless event broker for applications that respond to events from applications, SaaS services, and AWS services. Event buses route events across AWS accounts, and subscriptions can combine filters, targets, and retry policies. Buses support tens of thousands of subscribers, retention for up to 365 days, and JSON, Avro, Protobuf, and Cloud Events formats. EventBridge also supports ordered delivery and sharing a bus across accounts in an AWS Organization through AWS Resource Access Manager. Pipes connect endpoints point to point, with optional transformation, filtering, and enrichment. Supported SaaS sources can route events to AWS service targets; listed partners include Adobe, Datadog, MongoDB, Shopify, Stripe, and Snyk. API destinations send events from a bus or pipe to web applications on public or private networks. Monitoring uses CloudWatch metrics, with logging to CloudWatch Logs, S3, or Kinesis Data Firehose. IAM access controls, VPC endpoints, and TLS 1.2 encryption in transit are supported. AWS lists several compliance standards and HIPAA eligibility, while customers retain responsibility for their own compliance obligations.

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.