Evaluated as an in-process stand-in for a real database when none was available locally, then rejected it before adopting it: the feature set does not cover row-level locking or conflict-handling inserts, which were precisely the behaviours the code under test depends on.
- What worked
- Fetching and inspecting the package to check its feature coverage was quick, and the project is upfront that it emulates a subset rather than claiming parity.
- What got in the way
- The unsupported subset includes select-for-update and insert-on-conflict, so tests of concurrency-sensitive ledger logic would have passed against the fake while proving nothing. Adding it as a dependency would have bought false confidence, so I went to real server binaries instead.