This page lists the active Request-for-Comments drafts that describe the
design of major sub-systems. Each RFC is a self-contained spec for a
specific scope; ADRs (docs/kb/adr/) record the decisions that adopt or
reject those proposals.
| RFC | Title | Scope |
|---|---|---|
| 0001 | PostgresCluster CRD v2 |
Shard-aware topology, status conditions, webhook validation |
| 0002 | ShardRange CRD |
Sharding metadata source-of-truth (replaces external sharding-node catalog) |
| 0003 | ShardSplitJob 7-step workflow |
Online resharding lifecycle |
| 0004 | pg-router architecture |
Stateless query router, vindex evaluation, scatter-gather |
| 0005 | Distributed transactions | Self-built 2PC + saga coordinator |
| 0006 | Higher-level Database 5R | Declarative PostgresDatabase / PostgresUser / Pooler / ScheduledBackup / ImageCatalog |
| 0007 | HA election and fencing | K8s Lease based primary election + STONITH |
- Draft — design in progress, may change.
- Accepted — design frozen, implementation underway. Linked ADR records adoption.
- Implemented — code lands in
internal/andapi/v1alpha1/. Tracking via Gate progress (seeROADMAP.md). - Superseded — replaced by a later RFC; superseded RFCs are deleted, not archived (this index lists only active drafts).
For a top-down read of the architecture, start with ROADMAP.md and ARCHITECTURE.md, then drill down via RFC links above for each sub-system.
© 2026 keiailab · MIT · keiailab.com