Why CobbleDB split state, delivery, and serving: optimizing reads required rewiring updates
perplexity_ai · x · 2026-09-16
Perplexity explains the motivation behind CobbleDB's design: optimizing reads also required changing how updates reached the store, so durable document state, update delivery, and serving were separated across Pillar, Lorry, and CobbleDB, complementing the parallel batch-read design.
More from Infra
- AI Defense Agents Running 24/7 Could Send Token Costs Through the Roof — robleclerc · 2026-11-02
- LookAtMyQuant: a quantization compiler with 12x lower KL at Q4_K_M size on Gemma 4 E2B — teortaxesTex · 2026-11-02
- AI Data Centers Near a PC-Style Inflection Point: OCP Analysis of Power, Cooling, Networking — ai · 2026-11-02
- Cerebras halves in 5 months post-IPO: $25.4B order book leans heavily on OpenAI — FinanceYF5 · 2026-11-02
- Together launches post-training platform aligning RL training with serving — togethercompute · 2026-11-02
- Demis Hassabis: AI data centers should be beautiful — Recent_Fox4339 · 2026-11-02