SYSTEM Cited by 1 source
Nakadi¶
Definition¶
Nakadi (github.com/zalando/nakadi) is Zalando's open-source distributed event bus / event streaming platform. It wraps Apache Kafka with a REST-based publish / subscribe API, a schema registry, and per-event-type authorisation, so teams inside Zalando can produce and consume events without operating Kafka clients directly.
What makes it distinctive¶
- REST API over Kafka. Producers publish JSON events via HTTP POST to a Nakadi endpoint; consumers subscribe via HTTP long-poll. Hides Kafka protocol / partition management from application developers.
- Schema registry. Every event type has a declared JSON schema that Nakadi enforces at publish time — so consumers can rely on schema conformance.
- Partition + position management managed. Consumers track their offset via Nakadi's subscription API rather than directly managing Kafka offsets.
- Centrally managed inside Zalando — one shared event bus across the company.
Stub page — expand when a deeper Nakadi-focused source lands.
Seen in¶
- sources/2021-03-01-zalando-building-an-end-to-end-load-test-automation-system-on-top-of-kubernetes — named as a centrally managed event queue whose test- cluster deployment had to be adjusted for production-parity before the end-to-end Payment load tests could produce realistic throughput — called out as operational friction requiring cross-team alignment.
Related¶
- systems/kafka — Nakadi's underlying substrate.
- systems/zalando-load-test-conductor
- companies/zalando