Setting up Fisher, and deciding whether to Added in 1.8.0
Fisher (SQLite document + event store) setup and fit assessment — AddFisher bootstrapping, connection strings, DatabaseSchemaName folding into a table prefix, tables created on first use, the Solo-only async daemon and why HotCold is refused, WAL, the Polly resilience pipeline that earns its place because SQLite takes one writer per file, database-per-tenant as a performance feature, the conjoined-tenancy rules Fisher refuses to start without, and IntegrateWithWolverine.
Use when standing up a Wolverine + Fisher application, deciding whether a file-in-process store fits a deployment, or diagnosing SQLITE_BUSY, slow projections, a stale-projection timeout, a refused daemon mode, a 'Tenancy storage style mismatch' at startup, or a strong-typed id that LINQ will not filter or select.
Skill details
- Skill name:
fisher-setup-and-decision-guide - Applies to:
fisher,wolverine - Tags:
fisher,sqlite,setup,decision-guide,daemon,multitenancy,conjoined-tenancy,ef-core,resiliency,strong-typed-ids,RegisterValueType,StubEventStream - Added in: 1.8.0
- License: Proprietary. Copyright JasperFx Software LLC.