Apache Pulsar vs AWS Glue Schema Registry

Apache Pulsar is a free, open-source distributed messaging and streaming platform built for cloud use. It supports message consumption with less than 10 ms latency and up to one million unique topics in a cluster. Configurable replication across geographic regions and automatic client failover to healthy clusters support multi-region deployments. Tenants and policies control access to data and actions, and can isolate brokers to limit noisy-neighbor effects. Maintained client libraries are available for Java, Go, Python, C++, Node.js, and C#. Built-in connectors move data to and from systems including Kafka, RabbitMQ, MySQL, PostgreSQL, MongoDB, Cassandra, and Elasticsearch. Pulsar Functions process messages with user-defined logic in Java, Python, or Go. Tiered storage can offload data from BookKeeper to blob storage such as S3 for unlimited retention. It can run in Docker or Kubernetes, with a Helm chart for Kubernetes. Encryption, authentication, and authorization are available but are not enabled by default. The 5.0.0-M2 milestone is for early testing and feedback, not production use.

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.