Message type containing set of all PersistenceId received from the database.
An abstract journal used by PersistentActors to read/write events to a database. This implementation uses horizontal batching to recycle usage of the DbConnection and to optimize writes made to a database. Batching journal is not going to acquire a new DB connection on every request. Instead it will batch incoming requests and execute them only when a previous operation batch has been completed. This means that requests coming from many actors at the same time will be executed in one batch. Maximum number of batches executed at the same time is defined by MaxConcurrentOperations setting, while max allowed batch size is defined by MaxBatchSize setting. Batching journal also defines MaxBufferSize, which defines a maximum number of all requests stored at once in memory. Once that value is surpassed, journal will start to apply OnBufferOverflow(IJournalMessage) logic on each incoming requests, until a buffer gets freed again. This may be used for overflow strategies, request denials or backpressure.
All settings that can be used by implementations of BatchingSqlJournalTConnection, TCommand.
Settings used by CircuitBreaker used internally by the batching journal when executing event batches.
Default implementation of timestamp provider. Returns UtcNow for any message.
Class used for storing intermediate result of the IPersistentRepresentation in form which is ready to be stored directly in the SQL table.
Settings used for managing filter rules during event replay.
Class used for storing whole intermediate set of write changes to be applied within single SQL transaction.
Persisted event identifier returning set of keys used to map particular instance of an event to database row id.