Amazon EventBridge vs AWS Glue Schema 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.

AWS Glue Schema Registry is a free cloud service for centrally discovering, controlling, and evolving schemas used by streaming applications. It supplies serializers and deserializers so producers and consumers can share schema definitions during data exchange. Supported formats are Avro v1.11.4, JSON Schema Draft-04, Draft-06, and Draft-07, plus Protocol Buffers proto2 and proto3; Protobuf extensions and groups are not supported. Eight compatibility modes are available: NONE, DISABLED, BACKWARD, BACKWARD_ALL, FORWARD, FORWARD_ALL, FULL, and FULL_ALL. Features include automatic registration, metadata-based schema sourcing, IAM compatibility, and optional ZLIB compression. Documented integrations cover Apache Kafka, Amazon MSK, Kinesis Data Streams, Amazon Managed Service for Apache Flink, AWS Lambda, AWS Glue streaming, and Apache Kafka Streams. Client API traffic uses TLS over HTTPS, and schemas are encrypted at rest with an AWS KMS service-managed key. Registry ARNs organize permissions for schema operations.