Bifrost
Bifrost copied to clipboard
dolittle
This is the stable release of Dolittle till its out of alpha->beta stages
For instance when allocating sequence numbers - for things like Redis you might want to have a backing store other than Redis itself and therefor chain the result of allocation...
We need to put in place mechanisms for dealing with reliability related to the following: - Commands coming in - Events applied - Events published - Events stored - Events...
Today everything can fall back to EntityContext - an old abstraction that has served us well, but is no longer needed.
Today we have a system based on providing the capability of metadata related to things like paging. We call this QueryProviders. This should probably be called more specific what it...
Streaming - typically with a continuation token - should also be supported
Resources might be transiently unavailable and one need to retry. For reliability, Bifrost should have a mechanism for cross-cuttingly dealing with this - configurable for policy. Look at Polly.net: https://github.com/App-vNext/Polly...
Due to how SignalR wants everything registered before opening a connection, it is not registering itself for messages. This needs to be looked into. There is a thing with Hubs...
As we have with succeeded, failed - add similar for beforeExecute as well