meta: store feature parity tracking — all stores must have same capabilities #139

Closed
opened 2026-03-01 11:15:05 +00:00 by ash · 0 comments
Owner

Store Feature Parity Tracking

Full matrix committed to STORE_PARITY.md in repo root.

Sub-issues created:

  • #216 natsstore: ReadFromWithOptions
  • #217 natsstore: SubscriptionAdapter
  • #218 natsstore: Change Relay / Notifier
  • #219 natsstore: EventStoreWithArchival
  • #220 natsstore: Truncate
  • #221 natsstore: streamType parameter mismatch
  • #222 natsstore: persist tombstones
  • #223 sqlitestore: advisory locks
  • #224 sqlitestore: competing projections
  • #225 all stores: StreamTypeReader

pgstore is the most feature-complete. natsstore has the most gaps (7 issues). sqlitestore has 2 gaps (expected given single-process nature).

## Store Feature Parity Tracking Full matrix committed to `STORE_PARITY.md` in repo root. ### Sub-issues created: - #216 natsstore: ReadFromWithOptions - #217 natsstore: SubscriptionAdapter - #218 natsstore: Change Relay / Notifier - #219 natsstore: EventStoreWithArchival - #220 natsstore: Truncate - #221 natsstore: streamType parameter mismatch - #222 natsstore: persist tombstones - #223 sqlitestore: advisory locks - #224 sqlitestore: competing projections - #225 all stores: StreamTypeReader pgstore is the most feature-complete. natsstore has the most gaps (7 issues). sqlitestore has 2 gaps (expected given single-process nature).
ash closed this issue 2026-03-10 08:04:37 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ash/eskit#139
No description provided.