system-design

Design a scalable system architecture by converting product goals into functional and non-functional requirements, component diagrams, API contracts, and storage choices. This produces structured design documents with explicit assumptions and trade-off analysis.

Define service boundaries and API contracts by mapping data flows and component interactions for your platform. This process specifies service interactions, endpoint designs, and data models suitable for implementation planning.

System reliability and scale planning involves estimating load, choosing scaling approaches, and outlining monitoring strategies. It specifies caching, queue flows, and error/retry behavior to handle production failure modes.

Analyze trade-offs and failure modes by evaluating storage choices and data models against your engineering constraints. This generates explicit trade-off documentation covering retry behavior, error handling, and reliability impacts.

Yes, this system design approach supports event-driven ingestion and low-latency processing by defining queue flows, caching layers, and reliable service interactions. It outputs architecture diagrams and scaling plans tailored to these constraints.