travisjeffery/jocko

Health v2 · maintenance only

Adoption not part of the score

5012 stars · 371 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Jocko is a distributed commit log service implementing the Kafka protocol in Go, with built-in coordination via Serf discovery and Raft consensus so no ZooKeeper is needed. It ships as a single binary and aims to be protocol-compatible so existing Kafka clients like Sarama work with it.

Use cases

• run a kafka-compatible message broker without zookeeper
• self-host a lightweight event streaming broker in go
• deploy a distributed commit log as a single binary
• use kafka clients like sarama against a simpler broker
• learn how kafka storage and consensus internals work
• spin up a small kafka cluster for development or testing

When to choose

• you want kafka-style pub/sub or event streaming without operating zookeeper
• you prefer a single-binary, cloud-native deployment
• you're a go shop wanting a hackable broker implementation
• you need a lightweight kafka-compatible broker for dev/test environments

When to avoid

• you need full kafka feature parity such as consumer groups, replication, and complete protocol coverage
• you run mission-critical production workloads requiring battle-tested durability
• you depend on kafka ecosystem tooling that needs advanced protocol versions
• you need guaranteed long-term maintenance - the project has had hiatus periods

Facets

service · maturity experimental

message-queue streaming rpc microservices big-data developer-tools go self-hosted kafka-compatible commit-log event-streaming no-zookeeper raft-consensus serf-discovery single-binary messaging linux macos docker

Member repositories

For agents

markdown · JSON · MCP: product_card(name="travisjeffery/jocko")