3 posts
A Fisher store is one SQLite file, which makes backup sound trivial. Copying that file while the application runs silently loses committed writes. Here is the demonstration, the SQLite primitive that gets it right, and a hosted service that snapshots, verifies, compresses and ships every database to S3.
Event sourcing in Fisher: a sale as a stream, committing in the same transaction as your documents, projections across the lifecycles, and the async daemon. Plus the two places SQLite genuinely changes the semantics, where the exclusive append methods fail instead of waiting and where contiguous sequences make the high-water mark trivial.
Fisher is the Marten and Polecat programming model on SQLite, running inside your own process with no database server at all. A tour of the document side: identity, sessions, LINQ including joins and paging, expression indexes against generated columns, patching, optimistic concurrency, and the single-writer constraint everything else follows from.