Kafka, RabbitMQ and NATS
Kafka, RabbitMQ and NATS sit in the same tree as the databases, and their console reads what arrives. This first version only reads: nothing is published, and no topic or queue is created or purged.
Adding a broker
Brokers have a window of their own: Brokers in the Window menu. Add broker, choose the Product, Kafka, RabbitMQ or NATS, and give its address; RabbitMQ asks for a Virtual host as well. In the tree each is marked for what it is: Log broker, Queue broker or Subject broker.
The console of a broker
A broker’s console takes one of two commands instead of SQL, and the difference between them is the difference that matters: reading a Kafka topic costs nothing, taking a message off a RabbitMQ queue takes it away.
tail <source> [--partition <n>] [--from live|earliest|last:<n>|offset:<n>]
get <source> [--peek [--count <n>]]
tail follows a source and keeps the feed open; it starts at live unless told otherwise. get takes one message off a queue; with --peek it reads up to --count of them, a hundred at most, and puts them back. The run button says which it is about to do: Tail, Take or Peek.
Kafka
The tree lists the topics, and under each its partitions by number. tail reads a topic, or one partition with --partition, from where --from says, and the feed shows how far it is behind. Nothing commits an offset: there are no consumer groups, so reading here moves nobody else’s place. With a schema registry, Avro bodies are decoded; Protobuf and JSON Schema are not.
RabbitMQ
AMQP has no way to list what a server holds, so the tree says This protocol cannot list what a server holds: name the queue yourself. get takes one message off it, and says One message taken. It is off the queue. get --peek reads and puts back, which still moves the redelivery count of every message read, for good. tail is refused.
NATS
The tree lists the JetStream streams, with how each keeps its messages, and under each the subjects it is configured for. tail follows a subject; only a JetStream stream can be read from earlier with --from, since core NATS keeps nothing. get is refused.
The feed
A feed opens in its own panel and says whether it is Opening, Live or Stopped. Each message is a row with its key, when it was stamped, its size and its place: partition and offset, sequence, or delivery tag. Choose a message to read it, and its body shows beside. The panel keeps the newest messages, as many as Settings → Result → Rows per page, and counts the ones it let go. It runs until you close it.