Upgrade and migration
Troolio 10.0.8 is the first public five-package cohort: Core plus Agents, SQL Server, KurrentDB, and the combined KurrentDB/SQL adapter. Existing hosts on Core 10.0.5 should review package changes and provider requirements before upgrading. The new adapter IDs do not automatically activate routes or migrate data.
On this page
Prepare
- Inventory the current Troolio and Orleans versions, actor assemblies, stream formats, serializers, schemas, and hosted workers. Pin all chosen Troolio packages to 10.0.8.
- Back up event streams, SQL journals, projections, and operation evidence. Record the current route epoch and deployment fingerprint if a selected path is already in use.
- Build the application against the new packages and run actor replay tests with representative historical events. Check event type names and serialized bytes before any production rollout.
- Apply application-owned database migrations and verify connection, lock, ownership, retention, and erasure policies. Do not use disposable test schemas as production migrations.
- Test projection catch-up, retry identity, effect idempotency, and a worker crash near each provider boundary.
Roll out
Deploy compatible hosts and admit the reviewed serving cohort. For selected routes, promote the route epoch under its authoritative store and prevent older workers from writing. Watch append conflicts, projection backlog, effect intents, and broker journals. Keep rollback procedures tied to a verified state of streams and schema; event format changes may need a forward fix rather than a binary downgrade.
See packages, deployment checklist, and recovery.