system-design

To brainstorm distributed system architecture, you explore design options for new services and data flows, articulate tradeoffs, and converge on a clear recommendation without writing code. This process uses distributed-systems principles to evaluate storage strategies and consistency guarantees.

The best way to critique a system design proposal is to systematically review it for correctness, missing requirements, risky assumptions, idempotency, and failure handling. This yields a severity-ranked findings report highlighting operational gaps and failure modes.

Failure mode analysis in API design scrutinizes proposed data flows and consistency models to identify operational gaps and risky assumptions. It applies distributed-systems principles to produce a severity-ranked critique of the architecture's resilience.

Yes, you can use distributed-systems principles to plan consistency guarantees when selecting storage strategies and defining API surfaces. This ensures your architecture explicitly addresses tradeoffs and failure handling in the data flow.

A non-code system design approach limits output to structured design documents and severity-ranked critique reports rather than executable implementations. It focuses entirely on evaluating architecture tradeoffs and failure modes without generating actual code.

You should provide a diagram or detailed text for an architecture review to enable a thorough second-pass evaluation of your proposal. This allows the review to systematically assess correctness, idempotency, and failure handling.