# BabelQueue > BabelQueue is an open-source, broker-agnostic standard and set of SDKs that let PHP/Laravel, Symfony, Python, Go, Node.js, Java and .NET exchange queue messages over a single frozen strict-JSON envelope (`schema_version: 1`) whose job identity is a URN — no PHP `serialize()` anywhere on the wire. BabelQueue is a specification first and a set of libraries second. Six SDK cores implement it — PHP (with Laravel and Symfony adapters), Python, Go, Node.js, Java and .NET — and every one emits byte-compatible envelopes, so a job produced in one language is consumed natively in another. Seven brokers are GA and locked by a shared cross-SDK conformance suite: Redis, RabbitMQ, Amazon SQS, Azure Service Bus, Apache Pulsar, Apache Kafka and Apache ActiveMQ/Artemis. The envelope is frozen at `schema_version: 1`; identity is the URN in the `job` field, never a class name; `data` is pure JSON; and `trace_id` is preserved and forwarded unchanged across every hop, so one correlation id ties a whole chain of work together across languages. BabelQueue is MIT licensed and developed in the open at https://github.com/BabelQueue. Every page listed below also exists as raw markdown at its own URL with `.md` appended — for example `/docs/spec/1.x/envelope.md`. ## Specification - [Wire Contract](https://babelqueue.com/docs/spec/1.x/introduction/): The frozen, language-neutral contract every BabelQueue SDK speaks — the envelope, the URN identity, and the rules that keep all six languages byte-compatible. - [The Envelope](https://babelqueue.com/docs/spec/1.x/envelope/): The frozen BabelQueue message envelope (schema_version 1): every field, the meta block, cross-language data rules, producer/consumer rules and forbidden fields. - [URN Naming](https://babelqueue.com/docs/spec/1.x/urn/): How every BabelQueue message is identified — a stable urn:babel:: string instead of a class name, so any language can route on it. - [Broker bindings](https://babelqueue.com/docs/spec/1.x/broker-bindings/): How Redis, RabbitMQ, SQS, Azure Service Bus, Pulsar, Kafka and Artemis each carry the identical canonical envelope body in native broker metadata. - [Broker setup recipes](https://babelqueue.com/docs/spec/1.x/broker-recipes/): Quick-start recipes for pointing each BabelQueue SDK at Redis or RabbitMQ, with the exact connection per language and pointers to the other brokers. - [Dead-letter & tracing](https://babelqueue.com/docs/spec/1.x/dead-letter-and-tracing/): How a failed message lands on .dlq with an additive dead_letter block, and how trace_id is forwarded unchanged across every hop. - [Idempotency](https://babelqueue.com/docs/spec/1.x/idempotency/): The meta.id consumption contract and the opt-in dedupe helper every SDK ships (ADR-0022): a seen-set Store that skips already-processed messages. - [Idempotency Stores & the Effect Guarantee](https://babelqueue.com/docs/spec/1.x/idempotency-stores/): How the seen-set Store makes at-least-once delivery an exactly-once effect (ADR-0022): the three-method contract, backends and conformance fixtures. - [Transactional Outbox](https://babelqueue.com/docs/spec/1.x/outbox/): The optional transactional outbox every SDK ships (ADR-0029): write the business row and envelope in one transaction, then relay the bytes verbatim. - [Observability (OpenTelemetry)](https://babelqueue.com/docs/spec/1.x/observability/): How every SDK maps trace_id to an OpenTelemetry TraceID (ADR-0025), emits send and process spans and the standard metric set (ADR-0038, ADR-0039), and links hops with W3C traceparent (ADR-0028). - [Log correlation](https://babelqueue.com/docs/spec/1.x/log-correlation/): Put trace_id, meta.id and job on every log line a handler writes, with a short example for Go, Python, Node, Java, .NET and PHP. - [Per-URN Schema Validation](https://babelqueue.com/docs/spec/1.x/schema-validation/): Opt-in validation of a message's data block against a per-URN JSON Schema (ADR-0024), plus bqschema tooling to govern schemas in git and CI. - [GDPR Field Encryption](https://babelqueue.com/docs/spec/1.x/gdpr-field-encryption/): Field-level GDPR encryption across SDKs (ADR-0030): the x-gdpr-sensitive schema keyword, a caller-bound Cipher seam, and protect and unprotect helpers. - [DLQ Redrive & Replay-Bypass](https://babelqueue.com/docs/spec/1.x/redrive-and-replay/): Move dead-lettered messages back onto a queue with Redrive (ADR-0026) and skip already-fired side effects on replay with Replay-Bypass (ADR-0027). ## PHP - [Introduction](https://babelqueue.com/docs/php-sdk/1.x/introduction/): Meet the PHP core, babelqueue/php-sdk: the framework-agnostic envelope codec, contracts and dead-letter helpers behind the Laravel and Symfony adapters. - [Installation](https://babelqueue.com/docs/php-sdk/1.x/installation/): Install the PHP core with composer require babelqueue/php-sdk on PHP 8.2 and ext-json; optional broker clients are installed only if needed. - [Producing messages](https://babelqueue.com/docs/php-sdk/1.x/producing-messages/): Produce messages with the PHP core: build the canonical envelope with EnvelopeCodec, encode it, and publish through any transport. - [Consuming messages](https://babelqueue.com/docs/php-sdk/1.x/consuming-messages/): Consume with the PHP core: decode and validate the envelope, route by URN, and drive the Kafka and Pulsar consumers with the consume runtime. - [Transports](https://babelqueue.com/docs/php-sdk/1.x/transports/): Optional framework-less PHP transports for Redis, AMQP, SQS, Kafka, Pulsar and STOMP (Artemis), built on the one-method Transport seam. - [Reliability & governance helpers](https://babelqueue.com/docs/php-sdk/1.x/reliability-and-governance/): Opt-in reliability and governance helpers in the PHP core: idempotency, outbox, DLQ redrive, GDPR field encryption and OpenTelemetry (spans, metrics, traceparent). ## PHP / Laravel - [Introduction](https://babelqueue.com/docs/laravel/1.x/introduction/): Meet the Laravel driver: publish jobs as a strict JSON envelope with drop-in Redis, RabbitMQ, SQS and Artemis queue drivers, no PHP serialize(). - [Installation](https://babelqueue.com/docs/laravel/1.x/installation/): Install the Laravel driver with composer require babelqueue/laravel on PHP 8.2 and Laravel 11 or 12, then publish config/babelqueue.php. - [Configuration](https://babelqueue.com/docs/laravel/1.x/configuration/): Configure the Laravel driver: add a babelqueue-redis or babelqueue-rabbitmq connection in config/queue.php and map URNs to handlers. - [Producing messages](https://babelqueue.com/docs/laravel/1.x/producing-messages/): Produce messages in Laravel: implement ShouldQueuePolyglot and dispatch the job, or use the BabelQueue facade to publish a URN and payload. - [Consuming messages](https://babelqueue.com/docs/laravel/1.x/consuming-messages/): Consume messages in Laravel: map each URN to a handler class in config/babelqueue.php and run the standard queue worker as usual. - [Amazon SQS driver](https://babelqueue.com/docs/laravel/1.x/amazon-sqs/): The babelqueue-sqs drop-in Laravel driver: a polyglot Amazon SQS queue on the native sqs connection, with standard Laravel jobs passing through. - [Apache ActiveMQ Artemis driver](https://babelqueue.com/docs/laravel/1.x/apache-activemq-artemis/): The babelqueue-artemis Laravel driver: a polyglot Apache ActiveMQ Artemis queue over STOMP that interoperates with Java, .NET, Node, Python and Go. - [Reliability & governance helpers](https://babelqueue.com/docs/laravel/1.x/reliability-and-governance/): Use the PHP core's opt-in reliability and governance helpers from the Laravel driver: idempotency, outbox, DLQ redrive, GDPR encryption and traceparent, and how a failed message reaches failed_jobs or the DLQ. ## PHP / Symfony - [Introduction](https://babelqueue.com/docs/symfony/1.x/introduction/): Meet the Symfony adapter: keep Messenger transports, handlers and retry while a serializer switches the wire format to the BabelQueue envelope. - [Installation](https://babelqueue.com/docs/symfony/1.x/installation/): Install the Symfony adapter with composer require babelqueue/symfony on PHP 8.2 and Symfony 6.4 or 7, and enable the bundle for Messenger. - [Configuration](https://babelqueue.com/docs/symfony/1.x/configuration/): Configure the Symfony adapter: point a Messenger transport at the BabelQueue serializer and map each URN to a PolyglotMessage class. - [Producing messages](https://babelqueue.com/docs/symfony/1.x/producing-messages/): Produce messages in Symfony: implement PolyglotMessage and dispatch through Messenger, and BabelQueue encodes the canonical envelope. - [Consuming messages](https://babelqueue.com/docs/symfony/1.x/consuming-messages/): Consume messages in Symfony with a normal Messenger handler routed by message class, while BabelQueue decodes the envelope and bridges retry and trace. - [Broker transports](https://babelqueue.com/docs/symfony/1.x/broker-transports/): Run BabelQueue over any Symfony Messenger transport, built-in or third-party, with babelqueue.messenger.serializer; interop is body-authoritative. - [Reliability & governance helpers](https://babelqueue.com/docs/symfony/1.x/reliability-and-governance/): Reliability and governance in the Symfony adapter: idempotency and trace middleware, plus the core outbox, DLQ redrive and GDPR helpers. ## Python - [Introduction](https://babelqueue.com/docs/babelqueue-python/1.x/introduction/): Meet the Python SDK: a zero-dependency EnvelopeCodec plus a small BabelQueue runtime that publishes and consumes over eight URL-selected transports. - [Installation](https://babelqueue.com/docs/babelqueue-python/1.x/installation/): Install the Python SDK with pip install babelqueue, then add extras for Redis, RabbitMQ, SQS, Service Bus, Pulsar, Kafka or Artemis, plus OTel and GDPR. - [Configuration](https://babelqueue.com/docs/babelqueue-python/1.x/configuration/): Configure the Python SDK: point the BabelQueue runtime at a broker with a URL, where a scheme such as redis://, amqp:// or kafka:// picks the transport. - [Producing messages](https://babelqueue.com/docs/babelqueue-python/1.x/producing-messages/): Produce messages in Python: call app.publish with a URN and payload on the BabelQueue runtime, or build the envelope yourself with EnvelopeCodec.make. - [Consuming messages](https://babelqueue.com/docs/babelqueue-python/1.x/consuming-messages/): Consume messages in Python: register a handler per URN with @app.handler and run the worker, or decode the envelope with EnvelopeCodec yourself. - [Celery adapter](https://babelqueue.com/docs/babelqueue-python/1.x/celery/): Run the BabelQueue runtime on your existing Celery broker — from_celery(app) and install_worker(app) drain canonical envelopes alongside your Celery tasks. - [Django adapter](https://babelqueue.com/docs/babelqueue-python/1.x/django/): Settings-driven BabelQueue for Django — a BABELQUEUE config, get_app()/publish() helpers, and a manage.py babelqueue_worker command. - [Reliability & governance helpers](https://babelqueue.com/docs/babelqueue-python/1.x/reliability-and-governance/): Opt-in reliability and governance helpers in the Python core: idempotency, outbox, DLQ redrive, GDPR field encryption and OpenTelemetry (spans, metrics, traceparent). ## Go - [Introduction](https://babelqueue.com/docs/babelqueue-go/1.x/introduction/): Meet the Go SDK: a zero-dependency codec for the same JSON envelope as every other language, with an optional App runtime and seven broker transports. - [Installation](https://babelqueue.com/docs/babelqueue-go/1.x/installation/): Install the Go SDK with go get, add a transport module such as redis or amqp, and check the Go 1.26+ version requirement. - [Configuration](https://babelqueue.com/docs/babelqueue-go/1.x/configuration/): Configure the Go SDK: set the queue and trace_id on Make, annotate failures into a dead_letter block, and pick an unknown-URN strategy. - [Producing messages](https://babelqueue.com/docs/babelqueue-go/1.x/producing-messages/): Produce messages in Go: build the canonical envelope with Make, encode it with Encode, and publish the JSON bytes with your own broker client. - [Consuming messages](https://babelqueue.com/docs/babelqueue-go/1.x/consuming-messages/): Consume messages in Go: Decode the bytes from your broker, gate them with Accepts, and switch on the URN whichever language produced the message. - [Runtime & transports](https://babelqueue.com/docs/babelqueue-go/1.x/runtime-and-transports/): The optional zero-dependency Go App runtime (publish, consume, worker loop) and transport modules for seven brokers, from Redis to ActiveMQ Artemis. - [Reliability & governance helpers](https://babelqueue.com/docs/babelqueue-go/1.x/reliability-and-governance/): Opt-in reliability and governance helpers in the Go core: idempotency, outbox, DLQ redrive, GDPR field encryption and OpenTelemetry (spans, metrics, traceparent). ## Node.js - [Introduction](https://babelqueue.com/docs/babelqueue-node/1.x/introduction/): Meet the Node.js and TypeScript SDK: a zero-dependency envelope codec shipped as dual ESM and CommonJS with bundled types, for any broker client. - [Installation](https://babelqueue.com/docs/babelqueue-node/1.x/installation/): Install the Node.js SDK with npm install @babelqueue/core: Node 18 or newer, dual ESM and CommonJS, bundled TypeScript types, no runtime dependencies. - [Configuration](https://babelqueue.com/docs/babelqueue-node/1.x/configuration/): Configure the Node.js SDK: pass the queue and traceId to EnvelopeCodec.make, annotate failures as dead_letter, and choose an UnknownUrnStrategy. - [Producing messages](https://babelqueue.com/docs/babelqueue-node/1.x/producing-messages/): Produce messages in Node.js: build the envelope with EnvelopeCodec.make, encode it with EnvelopeCodec.encode, and publish the JSON with your own client. - [Consuming messages](https://babelqueue.com/docs/babelqueue-node/1.x/consuming-messages/): Consume messages in Node.js: decode the bytes, narrow them with the accepts type guard, and switch on the URN whichever language sent the message. - [Adapters & transports](https://babelqueue.com/docs/babelqueue-node/1.x/adapters/): The nine @babelqueue packages beyond core: BullMQ and NestJS adapters plus Redis, RabbitMQ, SQS, Service Bus, Pulsar, Kafka and Artemis transports. - [Reliability & governance helpers](https://babelqueue.com/docs/babelqueue-node/1.x/reliability-and-governance/): Opt-in reliability and governance helpers in the Node core: idempotency, outbox, DLQ redrive, GDPR field encryption and OpenTelemetry (spans, metrics, traceparent). ## Java - [Introduction](https://babelqueue.com/docs/babelqueue-java/1.x/introduction/): Meet the Java SDK: a pure-JDK envelope codec with its own JSON implementation and no forced Jackson or Gson, usable with any broker client. - [Installation](https://babelqueue.com/docs/babelqueue-java/1.x/installation/): Install the Java SDK from Maven Central as com.babelqueue:babelqueue-core with Maven or Gradle; it needs Java 17 and has zero dependencies. - [Configuration](https://babelqueue.com/docs/babelqueue-java/1.x/configuration/): Configure the Java SDK: pass the queue name and an optional trace id to EnvelopeCodec.make, annotate failures with DeadLetters, and set UnknownUrnStrategy. - [Producing messages](https://babelqueue.com/docs/babelqueue-java/1.x/producing-messages/): Produce messages in Java: build the canonical envelope with EnvelopeCodec.make, encode it with EnvelopeCodec.encode, and publish with your own client. - [Consuming messages](https://babelqueue.com/docs/babelqueue-java/1.x/consuming-messages/): Consume messages in Java: decode the bytes, gate them with EnvelopeCodec.accepts, and switch on the URN whichever language produced the message. - [Reliability & governance helpers](https://babelqueue.com/docs/babelqueue-java/1.x/reliability-and-governance/): Opt-in reliability and governance helpers in the Java core: idempotency, outbox, DLQ redrive, GDPR field encryption and OpenTelemetry (spans, metrics, traceparent). - [Spring Boot adapter](https://babelqueue.com/docs/babelqueue-java/1.x/spring/): The babelqueue-spring Spring Boot adapter: a Spring AMQP MessageConverter, an injectable publisher and auto-configuration for RabbitTemplate. - [Redis transport](https://babelqueue.com/docs/babelqueue-java/1.x/redis/): The babelqueue-redis transport: an envelope publisher and URN-routed consumer over the reliable-queue list pattern, built on Lettuce. - [Amazon SQS transport](https://babelqueue.com/docs/babelqueue-java/1.x/amazon-sqs/): The babelqueue-sqs transport — a canonical-envelope publisher and a URN-routed consumer over the AWS SDK for Java v2, on the framework-agnostic core. - [Azure Service Bus transport](https://babelqueue.com/docs/babelqueue-java/1.x/azure-service-bus/): The babelqueue-azure-servicebus transport: a canonical-envelope publisher and URN-routed consumer over azure-messaging-servicebus. - [Apache Pulsar transport](https://babelqueue.com/docs/babelqueue-java/1.x/apache-pulsar/): The babelqueue-pulsar transport — a canonical-envelope publisher and a URN-routed consumer over pulsar-client, on the framework-agnostic core. - [Apache Kafka transport](https://babelqueue.com/docs/babelqueue-java/1.x/apache-kafka/): The babelqueue-kafka transport — a canonical-envelope publisher and a URN-routed, process-then-commit consumer over kafka-clients, on the Java core. - [Apache ActiveMQ Artemis transport](https://babelqueue.com/docs/babelqueue-java/1.x/apache-activemq-artemis/): The babelqueue-artemis transport — a canonical-envelope publisher and a URN-routed AMQP 1.0 consumer over JMS (Jakarta Messaging), on the Java core. ## .NET - [Introduction](https://babelqueue.com/docs/babelqueue-dotnet/1.x/introduction/): Meet the .NET SDK: a zero-dependency envelope codec on System.Text.Json that reads and writes the same JSON envelope as every other language. - [Installation](https://babelqueue.com/docs/babelqueue-dotnet/1.x/installation/): Install the .NET SDK from NuGet with dotnet add package BabelQueue.Core: it targets .NET 8 and relies only on in-box System.Text.Json. - [Configuration](https://babelqueue.com/docs/babelqueue-dotnet/1.x/configuration/): Configure the .NET SDK: pass the queue and traceId to EnvelopeCodec.Make, annotate failures with DeadLetters.Annotate, and set UnknownUrnStrategy. - [Producing messages](https://babelqueue.com/docs/babelqueue-dotnet/1.x/producing-messages/): Produce messages in .NET: build the envelope with EnvelopeCodec.Make, encode it with EnvelopeCodec.Encode, and publish the JSON with your own client. - [Consuming messages](https://babelqueue.com/docs/babelqueue-dotnet/1.x/consuming-messages/): Consume messages in .NET: Decode the bytes, gate them with EnvelopeCodec.Accepts, and switch on the URN whichever language produced the message. - [Reliability & governance helpers](https://babelqueue.com/docs/babelqueue-dotnet/1.x/reliability-and-governance/): Opt-in reliability and governance helpers in the BabelQueue.Core package: idempotency, outbox, DLQ redrive, GDPR field encryption and OpenTelemetry (spans, metrics, traceparent). - [MassTransit adapter](https://babelqueue.com/docs/babelqueue-dotnet/1.x/masstransit/): The BabelQueue.MassTransit adapter: a System.Text.Json converter, an injectable publisher and bus setup so MassTransit speaks the canonical envelope. - [Redis transport](https://babelqueue.com/docs/babelqueue-dotnet/1.x/redis/): The BabelQueue.Redis transport: an envelope publisher and URN-routed consumer over the reliable-queue list pattern, using StackExchange.Redis. - [Amazon SQS transport](https://babelqueue.com/docs/babelqueue-dotnet/1.x/amazon-sqs/): The BabelQueue.Sqs transport — a canonical-envelope publisher and a URN-routed consumer over the AWS SDK for .NET, on the framework-agnostic core. - [Azure Service Bus transport](https://babelqueue.com/docs/babelqueue-dotnet/1.x/azure-service-bus/): The BabelQueue.AzureServiceBus transport: a canonical-envelope publisher and URN-routed consumer over Azure.Messaging.ServiceBus. - [Apache Pulsar transport](https://babelqueue.com/docs/babelqueue-dotnet/1.x/apache-pulsar/): The BabelQueue.Pulsar transport — a canonical-envelope publisher and a URN-routed consumer over DotPulsar, on the framework-agnostic core. - [Apache Kafka transport](https://babelqueue.com/docs/babelqueue-dotnet/1.x/apache-kafka/): The BabelQueue.Kafka transport: a canonical-envelope publisher and a URN-routed, process-then-commit consumer over Confluent.Kafka. - [Apache ActiveMQ Artemis transport](https://babelqueue.com/docs/babelqueue-dotnet/1.x/apache-activemq-artemis/): The BabelQueue.Artemis transport — a canonical-envelope publisher and a URN-routed AMQP 1.0 consumer over AMQPNetLite, on the framework-agnostic core. ## Cross-language examples - [Cross-language: Python or PHP → Go or Java over Redis](https://babelqueue.com/docs/examples/1.x/cross-language-redis/): A runnable demo — a Python or PHP service produces the canonical BabelQueue envelope and a Go or Java service consumes it from the same Redis queue. ## Scoped corpora - [Specification](https://babelqueue.com/llms-spec.txt): the wire contract — envelope, versioning, broker bindings — as one plain-markdown document - [PHP](https://babelqueue.com/llms-php.txt): every PHP documentation page as one plain-markdown document - [PHP / Laravel](https://babelqueue.com/llms-laravel.txt): every PHP / Laravel documentation page as one plain-markdown document - [PHP / Symfony](https://babelqueue.com/llms-symfony.txt): every PHP / Symfony documentation page as one plain-markdown document - [Python](https://babelqueue.com/llms-python.txt): every Python documentation page as one plain-markdown document - [Go](https://babelqueue.com/llms-go.txt): every Go documentation page as one plain-markdown document - [Node.js](https://babelqueue.com/llms-node.txt): every Node.js documentation page as one plain-markdown document - [Java](https://babelqueue.com/llms-java.txt): every Java documentation page as one plain-markdown document - [.NET](https://babelqueue.com/llms-dotnet.txt): every .NET documentation page as one plain-markdown document ## Blog - [Spring Boot and BabelQueue over RabbitMQ](https://babelqueue.com/blog/spring-boot-babelqueue-rabbitmq/): Wire the canonical envelope into a Spring Boot app: one MessageConverter, an injectable publisher, and @RabbitListener consumers that interoperate with every other SDK. - [How we measure the 2% overhead budget](https://babelqueue.com/blog/measuring-the-overhead-budget/): BabelQueue holds the codec to under 2% over plain JSON. Here's the marginal-cost method behind that number, why it's measured without a broker, and what it really costs. - [BabelQueue vs Kafka, gRPC, and the hand-rolled bridge](https://babelqueue.com/blog/babelqueue-vs-kafka-grpc-bridge/): Four ways to make queue messages cross languages, compared honestly — and why changing only the serialization beats new infrastructure or losing your framework. - [Cross-language dead-letter queues](https://babelqueue.com/blog/cross-language-dead-letter-queues/): Route failed and unroutable messages to a dead-letter queue any language can read, with a structured reason — opt-in, additive, and still schema_version 1. - [BabelQueue vs CloudEvents: two envelopes, different problems](https://babelqueue.com/blog/babelqueue-vs-cloudevents/): CloudEvents standardizes how an event describes itself across protocols; BabelQueue freezes what a queue job looks like so six languages run it. An honest comparison — the real overlap, the real differences, and where CloudEvents is the better choice. - [What is a polyglot queue?](https://babelqueue.com/blog/what-is-a-polyglot-queue/): A polyglot queue is a message queue whose jobs are produced in one language and consumed natively in another. Why language-native serialization blocks that, the failure modes teams actually hit, and what a working solution has to provide. - [Why the envelope is frozen at schema_version 1](https://babelqueue.com/blog/why-the-envelope-is-frozen/): Freezing the wire envelope is the whole product. Here's what 'frozen' means, what can still change, and how versioning keeps a v1 producer readable by every v1 consumer. - [Publishing polyglot jobs from Laravel](https://babelqueue.com/blog/publishing-polyglot-jobs-from-laravel/): Add BabelQueue to a Laravel app and publish jobs that Go, Python, Node, Java and .NET services consume natively — without changing your broker. - [PHP produces, Go consumes — over Redis](https://babelqueue.com/blog/php-produces-go-consumes-redis/): A PHP producer and a Go worker share one Redis queue, exchanging the identical JSON envelope — no shared class, and no PHP runtime on the Go side. - [BabelQueue 1.0 is here — polyglot queues, simplified](https://babelqueue.com/blog/babelqueue-1-0/): All six SDKs — PHP, Python, Go, Node.js, Java and .NET — are now published at 1.0.0, with a SemVer-stable API and one frozen wire envelope. ## Reference - [FAQ](https://babelqueue.com/faq/): the 8 questions teams ask before adopting BabelQueue, each answered in full - [Glossary](https://babelqueue.com/glossary/): 14 definitions of the vocabulary the wire contract uses — polyglot queue, wire envelope, `schema_version`, URN identity, `trace_id`, dead-letter queue, idempotency key, transactional outbox, redrive and broker binding - [About](https://babelqueue.com/about/): what BabelQueue is, who maintains it, how it is licensed and how to get involved ## Legal & contact - [Privacy Policy](https://babelqueue.com/privacy-policy/): What personal data babelqueue.com processes, why, who else handles it, and how to exercise your rights. The site sets no cookies and runs no analytics. - [Cookie Policy](https://babelqueue.com/cookie-policy/): babelqueue.com does not use cookies, localStorage, analytics or advertising scripts, so there is no consent banner. - [Terms of Use](https://babelqueue.com/terms-of-use/): Terms for using babelqueue.com: CC BY 4.0 site content, MIT-licensed software, acceptable use, no warranty and how changes take effect. - [Contact](https://babelqueue.com/contact/): How to reach the BabelQueue maintainer: email, the GitHub issue tracker, and how to report a security vulnerability privately. ## Optional - [llms-full.txt](https://babelqueue.com/llms-full.txt): every page listed above concatenated into one plain-markdown document - [RSS feed](https://babelqueue.com/rss.xml): releases, guides and updates - [GitHub organisation](https://github.com/BabelQueue): the standard, all six SDKs, the schema-governance CLI and the cross-SDK conformance suite - [PHP SDK on Packagist](https://packagist.org/packages/babelqueue/php-sdk): install with `composer require babelqueue/php-sdk` - [Python SDK on PyPI](https://pypi.org/project/babelqueue/): install with `pip install babelqueue` - [Go SDK on pkg.go.dev](https://pkg.go.dev/github.com/babelqueue/babelqueue-go): install with `go get github.com/babelqueue/babelqueue-go` - [Node.js SDK on npm](https://www.npmjs.com/package/@babelqueue/core): install with `npm install @babelqueue/core` - [Java SDK on Maven Central](https://central.sonatype.com/artifact/com.babelqueue/babelqueue-core): install with `implementation("com.babelqueue:babelqueue-core:1.15.0")` - [.NET SDK on NuGet](https://www.nuget.org/packages/BabelQueue.Core): install with `dotnet add package BabelQueue.Core`