Constraints: Technical and Organizational
You'll learn: How technical choices, standards, regulations, and organizational boundaries create fixed limitations that shape your architectural decisions.
What Are Architectural Constraints?
Unlike quality attributes (which you want to achieve), constraints are limitations you must work within. They're the non-negotiable boundaries of your solution space—think of them as the walls of a room where you must arrange furniture. No matter how clever your design, you cannot break through these walls.
Technical Constraints
These stem from technology choices and infrastructure realities:
- Platform limitations: Must run on Java 8 because that's what's deployed
- Integration requirements: Must use the existing Oracle database
- Protocol mandates: Must communicate via SOAP for legacy system compatibility
- Resource caps: Maximum 2GB RAM per container in the current cluster
You might inherit a constraint ("The CEO's nephew built this on MongoDB") or face environmental ones ("Deployment only happens monthly").
Organizational Constraints
These arise from business structure and policy:
- Budget limits: $50K ceiling for cloud infrastructure
- Team boundaries: Cannot modify the billing team's services
- Compliance requirements: HIPAA, GDPR, PCI-DSS mandates specific controls
- Standards and policies: All APIs must follow OpenAPI 3.0 spec
- Skill availability: Team only knows Python, not Go
Why They Matter
Constraints eliminate options before you even start designing. Recognizing them early prevents wasted effort exploring architectures that simply won't work. A brilliant microservices design means nothing if company policy forbids containers in production.
Key Takeaway: Constraints are fixed boundaries—technical standards, regulations, infrastructure limits, and organizational rules—that you must identify early because they eliminate entire classes of architectural solutions before you begin designing.