Some of the key differences: - Written in Go rather than Java/Scala (big benefit here IMO is getting a small static binary rather than having to run a JVM) -

Some of the key differences: - Written in Go rather than Java/Scala (big benefit here IMO is getting a small static binary rather than having to run a JVM) - Doesn't rely on Zookeeper - Is integrated with NATS (can extend NATS with Kafka-like semantics, but in the future will allow for abstracting NATS away entirely) - Uses gRPC for its API - Supports "wildcard topics" - e.g. a stream can listen to the topic "foo.*" and will receive messages published on "foo.bar", "foo.baz", "foo.qux", etc. - Allows for streams to be paused and subsequently resumed automatically when published to - on the roadmap is "auto-pausing" of sparsely used streams - Exposes an activity stream that allows you to respond to events such as streams being created, deleted, paused, etc. One advantage Kafka currently has is its consumer groups, which are on the roadmap for Liftbridge but not implemented yet. There's a more complete comparison available here: https://liftbridge.io/docs/feature-comparison.html https://liftbridge.io/docs/feature-comparison.html