This is a collection of q's and a's gathered from the ddd-cqrs-es slack, in no particular order.

Singleton per process lifetime, bit like httpclient. But, it depends if you are using subscriptions or not.

To be elaborated on later

Depends a bit on your use case. Bigger maxCount results higher network payloads and memory usage, but is more efficient in batching.

In general, you want to do paging over your stream(s) with a page value of 1 < x < 1000.

Your message types will outlive your .net CLR types. Moving events along namespaces will break stuff.

As an alternative, use a dictionary/map between your message types and the CLR type you want to deserialize your message into.

In the Event Store streams are like documents in a document database. See more details in the article at https://eventstore.org/blog/20130210/the-cost-of-creating-a-stream/

When prefetch is turned off this will result in a call to the server. From https://github.com/SQLStreamStore/SQLStreamStore/pull/49#issue-92659628