Skip to main content

AMQP 0-9-1

XCON Quee speaks AMQP 0-9-1, so the existing ecosystem — pika, amqplib, Java/Spring, go-amqp091 — works with no code changes. It is the distribution surface; the native SDK remains the full-power one.

Enable it by setting amqp_listen (e.g. 0.0.0.0:5672) in the config.

Connect & authenticate​

SASL PLAIN carries the bearer token as the password (any username). The AMQP vhost / maps to Quee's anchor vhost main; /x maps to vhost x.

creds = pika.PlainCredentials("quee", TOKEN)
pika.BlockingConnection(pika.ConnectionParameters("SERVER", 5672, "/", creds))

What's supported​

  • Work queues — durable queues, competing consumers, basic.ack / basic.nack / basic.reject, basic.qos prefetch.
  • basic.get — synchronous pull.
  • Exchanges — direct, fanout, and topic (full */# grammar), evaluated at publish time. Durable exchanges + bindings survive a restart.
  • RPC — exclusive / auto-delete reply queues (see RPC).
  • Publisher confirms — a confirm is the engine fsync.
  • Message properties — content-type, headers, correlation-id, reply-to and the rest round-trip.

See the mapping for how each verb maps onto the log, and the limits for what is honestly refused.