Mainbrella on backend creation and idempotent retries
What happened
On October 8 the Hacker News front page covered a Mainbrella engineering blog post on backend creation and retries: the machine start command has already run, but the caller never got the result, so retrying is risky. Its approach gives each account a Cloudflare Durable Object as a persistent coordinator that serializes admission, reserves slots and quota, then starts machines in parallel outside the lock. Creation requests must carry an Idempotency-Key, and the account atomically writes a reservation record and a creation receipt. Receipts are kept for 24 hours, and pending reservations get a 90-second reconciliation window.
Written by AI from the coverage · updated 1 hour ago
Coverage
Follow the reports to see the story from different sides.
- Hacker News front pageWhen the machine boots but the reply disappears
Mainbrella 工程博客剖析其后端一个反复出现的问题：命令已执行但调用方看不到结果，重试因此变得危险。其方案是给每个账户配一个 Cloudflare Durable Object 作为持久协调器，串行化准入并预留槽位与配额，再在锁外并行启动机器。创建请求需携带 Idempotency-Key，账户会原子写入预留与创建回执，回执保留 24 小时，待定预留有 90 秒对账窗口。
Heat over time
Not enough continuous observations to draw a trend yet.