BROKABROKA
Sign inDownload CommunityRequest a demo
Documentation112 pagesOlder version — go to 1.1.0
Guides

BROKA documentation

Operate Kafka, Redis, RabbitMQ and Apache Artemis (formerly ActiveMQ Artemis) from one console — plus Memcached, which is a cache rather than a broker and is operated as one. Connect them, set up the people and guardrails around them, and read what every screen actually does. Every page applies to the self-hosted product — there is no hosted variant to keep track of.

112 pages · version 1.0.1 (BROKA 1.0.1) — an older release · applies to Community and Commercial unless a page says otherwise

Getting started

6

What BROKA is, and the handful of ideas the rest of the documentation is built on.

Deployment

3

Platform administration

15

Environments, connections, people and the guardrails between them — the parts that are the same whichever broker you run.

Kafka

24

Clusters, brokers, topics, consumer groups, producing and consuming, schemas, ACLs and credentials, Connect, transactions, quotas and client metrics.

Redis

18

Instances, clusters and Sentinel, the keyspace and its keys, Streams and their consumer groups, pending entries, memory, Pub/Sub, ACLs, search indexes and tools.

RabbitMQ

15

Connections, exchanges, queues of all three types, routing, dead-letter flows, policies, shovels and federation, users and definitions.

Apache Artemis

15

Addresses and their queues, messages browsed and operated on, connections and sessions, diverts, address settings, cluster and replication, users and in-doubt transactions.

Memcached

6

Nodes rather than a cluster, memory and slab classes, keys read one at a time or listed on request, and the live event log.

Operations

10

Day-two work: the dashboard, alerts and search, hardening, reviewing the audit trail, investigating an incident, and troubleshooting.