Alexander Berl

Main use case: Rewrite a stream into a "compacted" version to be able to eventually delete or archive the (high frequency) source stream(s) or keep those internal and publish only...

The EventStoreDB API contains a state for projections - this is useful to do logic depending on previously seen events. Also, persisting that state makes the projection able to resume....

Note: Setting expectedVersion to `myProjection.position` like above would only work if every source event leads to exactly one projected event! That is not necessarily the case. The API for a...

On top of this, the addition of a `linkTo()` function argument would be easy to add, which would allow to create streams that index arbitrary events of other streams. With...

Regarding naming: A projection that emits events is called a `ProcessManager` in a higher level. Also, a generic "projection" is currently called a "Consumer", so calling an emitting Consumer "Projection"...

Index range reading should return a generator and work with the same semantics as partition reading. Hence, the underlying file abstraction could be shared between index and partition.

See https://gist.github.com/albe/39c7b79f46daa49d2cf373ffab3c4513 -ugh

The feedback on nodejs/help repo suggests this is to be expected, as typed arrays do a bit more. After some testing with creating a custom implementation of a "buffer view...

This needs to be rewritten to only deal with unfinished commits as the torn writes has already been covered by #155

The EventStore read API should not be dealing with internal document sequence numbers and timestamps, so that part should not change. The goal though is, that the storage sequence number...