thanks for the reply!
I'm aware that Kafka is low-level (and that there is kmq, which tries to implement a message queue on top of it https://github.com/softwaremill/kmq/ ), but the exactly-once semantics seems isomorphic to having the sender and the receiver doing a 2 phase commit using the log.
what are MQ's guarantees? how are they implemented?
If you want throughout, Kafka is the better option. Use MQ for transaction processing.
Technically, Kafka is an event streaming solution, not a message queue. There's plenty of good literature out there if you want to dig deep into the difference.