system-architect

To document architecture decisions, generate an Architecture Decision Record (ADR) that compares options, explains trade-offs, and records the final choice based on your explicit requirements and constraints.

Defining service boundaries and data ownership requires a system design approach that accounts for your actual team size, latency needs, and failure modes rather than over-engineering for hypothetical futures.

Choosing between Kafka and SQS involves comparing the technologies against your specific constraints, scale assumptions, and consistency choices to produce a right-sized, failure-aware recommendation.

Designing an API surface and data model requires explicit requirements and optional alternatives to produce right-sized recommendations; without them, the architectural trade-offs cannot be accurately evaluated.

You need an ADR when justifying architecture decisions between specific technologies or patterns, whereas a general system design defines service boundaries, API surfaces, and data models for new components.

Yes, this system design approach accounts for operational fit by evaluating team size, latency needs, scale assumptions, and failure modes to prevent over-engineering for hypothetical futures.