Single Node First: When to Distribute

Single Node First: When to Distribute A workflow diagram generated by Archify. 01 / Business Need 02 / Scaling Decision EX / Distributed Cost Start simple Evaluate drivers Distribute and pay the cost What distribution costs you New Service · data-intensive app · Business Need › Start simple New Service data-intensive app Single Node First · Postgres, DuckDB, SQLite · Business Need › Start simple · simpler and cheaper Single Node First Postgres, DuckDB, SQLite simpler and cheaper Stay Single-Node · scale up, tune queries · Business Need › Evaluate drivers Stay Single-Node scale up, tune queries Limit Reached? · volume, QPS, latency · Scaling Decision › Evaluate drivers Limit Reached? volume, QPS, latency Name the Driver · HA, scale, latency, legal · Scaling Decision › Evaluate drivers · pick minimal scope Name the Driver HA, scale, latency, legal pick minimal scope Distribute · replicas, shards · Scaling Decision › Distribute and pay the cost Distribute replicas, shards Failure Modes · timeout, retries · Distributed Cost › What distribution costs you › Distribute and pay the cost Failure Modes timeout, retries Mitigation Budget · idempotency, tracing · Distributed Cost › What distribution costs you › Distribute and pay the cost · never free Mitigation Budget idempotency, tracing never free introduces minimal scope start here yes no budget for grow until it hurts Legend Agent logic Policy Tool action Context / trace Cloud service External system