I think Kafka is primarily for streaming data in the first place. I use colloquial definitions, but streams are not events from my point of view. So something like activeMQ or rabbitMQ seems to be more fitting for event sourcing. Don't know the tools the author did suggest.<p>But I think the most important differentiation is whether you have streams or messages.<p>That said, the ability to roll back to a previous "state" of an event queue is pretty nice in Kafka. But if you don't want to scale ad infinitum a more common message broker might be more fitting for consuming events. I only used Kafka in an experiment, I have no in depth knowledge.