There are many overlapping use cases and many where they are not
comparable. As example kafka does not work well as an eventstore as of
the last time I checked as there are some key features missing. 1) a
write in ES when acked means its actually written to a quorum of disks
in kafka its not written on any. 2) In an event store the ability to
get consistency is important (this does not exist there) 3) ES assures
idempotency again nothing 4) the entire concept of
projections/querying. Kafka is however significantly faster though the
largest reason is the durability vs no durability assurance. As a
transport kafka works really well.
> --
> You received this message because you are subscribed to the Google Groups
> "Event Store" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
event-store...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.
--
Studying for the Turing test