Constraints

Constraints narrow the solution space: budget, team size, existing tech stack, regulatory rules, third-party API limits, time to market, and data residency. Naming them early avoids proposing a perfect design the organization cannot build or operate.

Distinguish hard constraints (GDPR data location) from soft preferences (we like PostgreSQL). Explain how each constraint pushes you toward or away from specific patterns like multi-region active-active or managed services.

On interviews: ask about team expertise, existing systems, and compliance; show how constraints change your storage or messaging choice.

Common pitfalls: ignoring vendor rate limits; designing multi-region without budget discussion; assuming greenfield when legacy integration is required.

The trade-off is flexibility versus complexity—know when the simpler path is enough.

Checklist:

• List technical, legal, and organizational constraints.
• Separate hard limits from preferences.
• Explain how constraints affect major components.
• Mention dependencies on external systems.