The Polyglot Seam

The polyglot claim of the bus is easy to state and easy to doubt: any runtime that speaks the protocol is a first-class peer. The stream tier is where it stops being a slogan, because a consumer group makes the claim concrete. A subscription is not an object inside the BEAM; it is state that lives with the stream, on the Valkey server. Joining it is issuing XREADGROUP against a key — something a Go program, a Python worker, and a BEAM node do identically, because there is nothing runtime-specific to join.

Turn that around and the supersession is sharp. PubSub's fan-out lives in the runtime that owns the topic, so a second language needs a bridge, and a subscriber that blinks loses whatever arrived while it was gone. The stream tier keeps the subscription — cursor, pending lists, and all — on the server, so a non-BEAM consumer stands in the same group as the BEAM consumers, drains the same pending list, and gets the same at-least-once guarantee. The seam is not a translation layer; it is the absence of one.

It is worth being precise about what makes this polyglot, because it is not a feature that was added — it is a bridge that was never needed. A conventional broker offers per-language SDKs: a Go library, a Python library, each re-implementing the client's half of a bespoke protocol, each a place for the languages to disagree. The stream tier has no such surface. The protocol is Valkey commands, the subscription is server-side group state, and the payload is a branded claim a few bytes wide. A new language is not onboarded; it already has a Valkey client, so it already has everything it needs.

This is the streams-shaped form of the wire rule from the previous module: there, the point was that the protocol is the database's own wire, so any runtime that speaks it is a peer. Here the point is narrower and more concrete — the subscription is on the wire too, so peers do not merely issue the same commands, they share the same durable delivery. A Go consumer and a BEAM consumer are not two systems integrated; they are two members of one group, and the group cannot tell them apart. The conformance suite makes the equality a test rather than a promise, standing a non-BEAM reader in the group and draining the same pending list the BEAM does.

The polyglot rule — the subscription lives in Valkey, so any language joins the same group. PubSub's fan-out dies at the runtime boundary; a consumer group is server state — one cursor, one pending list — so a Go reader and a BEAM node share one stream and one at-least-once guarantee, with no bridge between them.