From how I read Greg, EventStore is like bacon - *everything* is better with
Not disputing the value of bacon, but some sort of documentation of
why and when one should use exactly this EventStore (rather than, for
example, joliver's) would be very valuable to my team as well. We're
about to start a project using CQRS, and while still gathering
requirements for the application, we're contemplating what EventStore
implementation to use.
In particular, there are a few keywords on the main page that seem to
be unique selling propositions to the EventStore right now, but I'm
missing in-depth explanations of them (at least I couldn't find them
on the "Docs" part of the website):
- Multi-Node: When would I want to use Multi-Node? And how does
Multi-Node work, exactly? Is this different from having a
SQL-Server-based event store with SQL replication and fail-over?
- Projections: What exactly are projections for? How would I use them
in a typical CQRS-based application/bounded context? Or would I, even?
Is this to replace event handlers on the query side?
- Monitoring Tools: What tools are there? What can I do with them?
As I said, we'll soon need to choose an event store for our
application, and this info would make the decision easier for us.