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
- First M5 Ultra Geekbench leak: 52,516 multi-core, ~35% faster than M3 Ultra — jedisct1 · 2026-09-16
- Apple execs on podcast: 2nm silicon, doubled Neural Engine, edge AI future — BenBajarin · 2026-09-16
- Sentdex's get-rich trick: buy 8 RTX Pro 6000s, resell 4 boxed, keep 4 free — Sentdex · 2026-09-16
- Google's Retrieve-for-Train replaces heavy autoregressive inference with a lightweight RL-trained diffusion model — gaganghotra_ · 2026-09-16
- Cerebras founder on the wafer-scale bet, chip supply chain, and training-to-inference pivot — AccBalanced · 2026-09-16
- IBM runs 753B MoE on 544 H100s with llm-d, serving 3,000 concurrent coding agents at 5-10x lower cost — dl_weekly · 2026-09-16