We’ve just released TimeoutMigrationTool 1.0.0.
Why should you migrate to native delayed delivery?
As the platform is moving towards native delayed delivery for all transports the timeout manager will be phased out eventually. This means that, should your system contain timeouts far out in the future, these timeouts would need to be migrated at some point in order to be able to update to newer versions of the platform. Run the
preview command to check if a migration is required.
1.0.0 of the tool supports migrating timeouts into RabbitMQ native delayed delivery from the following versions of persistence:
Please reach out to us if you have needs for a specific combination of storage and transport that should be considered.
Important considerations before starting
- The documentation contains detailed information about how the tool works, make sure to read it through before migrating
- Run the
previewcommand to validate the migration
- It is recommended to run the migration in a test environment first to ensure that everything works as expected
- Reach out to our support team if you experience any problems
Where to get it
You can install the tool from NuGet using:
dotnet tool install Particular.TimeoutMigration -g
The team in Particular