Distributed event store

[jmajoor]

I was looking at the event store capabilities of Marten, but from what I can gather from the documentation it won't be able to support distributed database environments.

In our event environment, the only thing that matters is the timestamp of an event. There are different types of events and different event streams, but we use the timestamp for determining the state of events at a certain point. I noticed you have a version number and a sequence ID associated with events. In our system there can be correlations between different event streams and these are all based on time. In your implementation it seems that each stream will get its own version number instead of just based on time.

In a distributed database environment, this sequence and version number won't work properly. Events can be written on different hosts in the cluster, which would then lead to duplicate version numbers and most likely duplicate primary key values (as part of replication of data).

Is it possible to configure the event store in such a way it is purely timestamp based and not sequence based?
Or are there other configuration options to make this work in a distributed (multi master) database?

[jeremydmiller]

@jmajoor No, sorry, this has never come up before. I think it would be easier to write something bepoke than alter Marten to fit that workflow.