Hi,

I have a question regarding backup order of *.chk files themselves.

If I understand various bits of info from documentation, Github issues and Google Groups, content of chaser.chk is pointer to position (in chunk files "continuum") reached by chaser process, while writer.chk is pointer to position reached by writer process. Chaser process should always be behind the writer (or at the sam

Just highlighting this in case you're interested, I took a fork of @dennisfabri racetimes example and extended it to run with Azure Functions and then extended again to publish to Azure EventGrid as a new extension inspired by the RabbitMQ example. Might be of interest to others.

https://github.com/craignicol/Eventflow.Example.Racetimes/tree/feature/event-grid-as-extension

To help onboard new users it would be useful to describe the main building blocks required to start using Commanded and configure an event store.

• Commanded.Application - explain what it is, and that it differs from an OTP application.
• Event store - adapter configuration and event store definition (e.g. define EventStore module).

It will be more helpful to pick up the library especially when the documentation is not updated.

I am working on this repo, but haven't fully declared the types when I'm still understanding the library.
https://github.com/beenotung/typestub-eventstore

As a follow-up to #209, which fixes this bug for SqlStreamStore (the presence of the bug has its roots in #175)

There's a lack of coverage of the writing an event with a null content for the Data field

I believe Equinox.Cosmos has coverage, but the SqlStreamStore + EventStore integration tests do not cover it.

Fix is to include a test scenario that generates an Event union with no bod

Intro (skip it if you are in a hurry ^^ )
A few weeks ago I started a new project and keeping all data in memory and just persist a log of events is a perfect match for the requirements. I started implementing my own solution (protobuf on filesytem to persist the journal, events and an in memory projection of the data).

A few days ago I found this project and it looks like someone took my

The README.md is missing how the type registry integrates, the docs no longer match the examples.

As stores are growing we should be having CI/CD and publishing to nuget automated. Just to lower down a burden on maintainer.

Also, we have docs and site deployment as well. Mostly github docs. (I guess we might need more than something to readme. as mentioned in #34 :) )

Description

Documentation should contain a working guide on how to get this set up - The "Getting started" video on Vimeo seems outdated as setting the project up as described brings in errors about Owin context in /Bifrost/Application.
And the Getting Started guide (DIY version) brings up the same error.

The documentation also misrepresents the project as its mapping to HumanResourced/

The reader for the CosmosDB ChangeFeed emits an (indicative, depends on clock sync) "age" stat per batch retrieved, which can be very useful as an indicator for troubleshooting

The same should be added to [the equivalent logging in EventStoreReader](https://github.com/j