InMemoryPersistencehas been renamed and moved to a dedicated package called the
Some scenarios require a non-durable persistence such as the development environment or a lightweight client not interested in durability across restarts:
Persistence at a glance
For a description of each feature, see the persistence at a glance legend.
|Storage Types||Sagas, Outbox, Subscriptions|
|Concurrency control||Optimistic concurrency|
|Scripted deployment||Does not apply|
|Installers||Does not apply|
endpointConfiguration.UsePersistence<InMemoryPersistence, StorageType.Sagas>(); endpointConfiguration.UsePersistence<InMemoryPersistence, StorageType.Subscriptions>(); endpointConfiguration.UsePersistence<InMemoryPersistence, StorageType.Timeouts>(); endpointConfiguration.UsePersistence<InMemoryPersistence, StorageType.Outbox>();
As delayed retries are enabled by default, using this persistence with a transport that uses the timeout manager has the risk of losing messages that have failed processing and are waiting for another retry attempt. Use this persistence only in scenarios where it is acceptable to lose messages.
The in-memory gateway deduplication persistence uses an LRU cache. By default this cache can contain up to 10,000 items. The maximum size can be changed using the following API.
var persistence = endpointConfiguration.UsePersistence<InMemoryPersistence, StorageType.GatewayDeduplication>(); persistence.GatewayDeduplicationCacheSize(50000);
When simultaneously handling messages, conflicts may occur. See below for examples of the exceptions which are thrown. Saga concurrency explains how these conflicts are handled, and contains guidance for high-load scenarios.
Starting a saga
System.InvalidOperationException: The saga with the correlation id 'Name: OrderId Value: f05c6e0c-aea6-48d6-846c-d1663998ebf2' already exists
Updating or deleting saga data
Non-durable persistence uses optimistic concurrency control when updating or deleting saga data.