You don’t have enough points to run this tool（9 pts）。 Buy points →
🏛️ Architecture Review
Describe your proposed design and get a critical, opinionated review — genuine strengths, the risks with recommendations, the tradeoffs you're making, and the questions to answer before building.
- Opinionated, not generic. Names real failure modes — scaling, consistency, cost, ops.
- Risks with fixes. Each concern comes with a concrete recommendation.
- Surfaces the tradeoffs. Makes the implicit choices and open questions explicit.
See the quality — a real example
Sample only · no credits usedInput — proposed design
One Postgres for everything; 6 microservices talking over synchronous HTTP, no queue; all on a single VM; target 5,000 req/s.
Output — review
Summary: Fine for an MVP, but the synchronous mesh and single VM are what will page you first.
- Availability: the single VM is a SPOF. → Run ≥2 instances behind a load balancer; use managed Postgres with a standby.
- Coupling: sync HTTP across 6 services means one slow hop stalls the whole chain. → Add a queue for non-critical paths; set timeouts + circuit breakers.
- Scale: 5k req/s will exhaust Postgres connections. → PgBouncer + read replicas.
Open question: what's your read/write split and acceptable RTO?
Sign in to use this tool
Sign in to use (30 free points on signup). Signed-in users run every tool on their account points — nothing to paste.
Sign in →