-
Notifications
You must be signed in to change notification settings - Fork 0
Milestones
List view
Decision issues that re-price the AI-era and reversible-or-deferred surfaces now that v1 has shipped, each weighed explicitly against the lowest tenets (Scalable, then AI-Driven) and the Simple / binary-size budget. No build work lands under these; each resolves to a recorded ADR and, if accepted, a scoped follow-up design issue gated by the no-claim-without-its-test rule (#14). Contains: off-path vector similarity search (vector sets); probabilistic membership types beyond HLL (Bloom-first); a native JSON document type stance; and a re-evaluation of the reversible Redis Streams non-goal (#12 / closed #132). Competitor pull as of mid-2026: Redis 8.x core (vector sets, BF/CF/CMS/TOPK/TDIGEST, RedisJSON), Valkey 9.1 + valkey-search/valkey-bloom/valkey-json, Dragonfly v1.39, Garnet 2.0 preview.
No due date•4/4 issues closedThe highest-value, charter-aligned compatibility gaps that every live competitor (Redis 8.8, Valkey 9.1, Dragonfly v1.39, Garnet 2.0 preview) now ships and IronCache lacks, each reusing machinery IronCache already has. Contains: (1) Hash-field TTL family HEXPIRE/HGETEX/HSETEX/HGETDEL/HPERSIST, P0; (2) CLIENT TRACKING / server-assisted client-side caching, P0; (3) Sharded Pub/Sub SSUBSCRIBE/SPUBLISH, P1; (4) DEBUG conformance subcommand subset, P1; (5) Native compare-and-set primitives SET IFEQ / DELIFEQ / MSETEX, P1; (6) Observability command parity INFO COMMANDSTATS/ERRORSTATS + HOTKEYS, P2; (7) Command-surface completeness micro-commands LOLWUT / BITOP set-algebra, P2. Rationale: Compatible is the top tenet and 'the world's best redis cache' is judged first on the wire contract. Per-field hash TTL and client-side caching are the two most cache-shaped features in the modern Redis surface, both now table stakes across all four open competitors, and both extend existing IronCache subsystems (the per-shard timing wheel #51 and the RESP3 push substrate in pubsub.rs that already names CSC as its designed-for shape). The DEBUG subset disproportionately serves IronCache specifically: it unlocks running the upstream Redis/Valkey TCL conformance suites unmodified, directly reinforcing the headline differential-tested claim and the governance rule that no claim ships without its test. Native CAS gives clients atomic optimistic concurrency without Lua, which actively reinforces hard non-goal #1 rather than eroding it. Together this milestone closes the visible compatibility delta at the lowest implementation risk.
No due date•7/7 issues closedThe RPO=0 end-state for clustered deployments: upgrade the in-sync raft replica, promote (committed-log fence), upgrade the old primary. Needs prod running clustered.
No due date•1/1 issues closedRemove the upgrade downtime on a single node: systemd socket-activation (no connection-refused) + a fast state handoff (tmpfs / streamed old->new) with a -LOADING cutover freeze.
No due date•3/3 issues closedironcache upgrade MVP: the verified self-updater spine (fetch/verify/atomic-swap/health-gate/auto-rollback) + a data-safe snapshot-reload swap with a write-freeze. Works on the single-node prod box; loss-free, brief downtime.
No due date•4/4 issues closedCritical-path gate: these issues must be resolved or fully specified before the first implementation PR merges. Sequence is in docs/ROADMAP.md and the roadmap tracking issue; waves are the wave:0..3 labels.
No due date•43/43 issues closedDecisions resolved to the point a prototype can be built.
No due date•58/58 issues closedThe subsystem design specifications and their decisions.
No due date•47/47 issues closedTenets, scope, committed non-goals, and the research foundations.
No due date•17/17 issues closed