Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities.
Decisions and outputs
Decisions
Use the Business Impact Canvas to identify availability, security, and data risks that influence architecture options.
Use the Locations Canvas to capture geopolitical, regulatory, network, residency, and trust-boundary constraints.
Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.
Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.
Compare viable architecture styles against the gathered requirements and document the selected pattern and rationale.
Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.
Outputs
A justified architecture choice
Documented risks, locations, capacity, security, privacy, and operability constraints
Clear rationale for API, event, file, stream, data product, direct integration, or hybrid implementation style
architecture-decision
documentation
platform-config
metrics
Recommended resources
Facilitate as API Architect
Use these prepared prompts alongside the stakeholder decisions, outputs, stations, and resources summarized above.
AI facilitation
Prompt pack
Facilitate a station with API Architect
facilitate-station
Stakeholder: API Architect
Cycles: API Productization Cycle, Integration Productization Cycle
Stations: Architecture & Platform Decisions
Resources and canvases: Business Impact Canvas, Locations Canvas, Capacity Canvas
Act as an APIOps Cycles facilitator. Use the selected station questions, entry criteria, exit criteria, stakeholders, and related resources to guide the discussion. Produce decisions, evidence gaps, and next steps.