feat: Add PACELC When-To-Use Guide For Six Backends - #19
Merged
Conversation
Typed catalog plus a constraint-then-score chooser so consistency, query shape, write scale, and ops cost stay comparable.
preferConsistency now orders by isolation class, with durable cross-key stores ahead of per-key Redis. README includes the exact renderGuide() tables so the written guide cannot drift.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We have six backends and a latency bench, but picking a store was still a README ramble. This adds a typed catalog for PACELC consistency, native query shape, write scale, and ops cost, plus chooseStore which eliminates on hard constraints then ranks what is left.
Postgres stays the default for this feed (integrity plus a join). Hops go to Neo4j, TTL to Redis, SQL plus linear writes to Cockroach, and a write-heavy timeline to Cassandra. Conflicting constraints (hops and TTL) return an empty ranking instead of a fake compromise. renderGuide() is generated from the same catalog so the tables cannot drift.
Closes #18