architecture-review

An architecture review checklist covers context boundaries, non-functional requirements, security controls like OIDC and TLS, integration patterns such as outbox and idempotence, and observability including logs, metrics, and traces.

Check bounded context boundaries by verifying the absence of direct dependencies on external databases and ensuring clear context separation across code, infrastructure, and data flows during gate reviews.

Use a checklist-driven architecture review during merge gate reviews, when adding new integrations, or when modifying bounded contexts to ensure compliance with security, NFRs, and observability standards.

Verify non-functional requirements by confirming they are measurable with proof of execution, and check security controls by validating OIDC, TLS, and audit logging implementations against the standardized checklist.

Architecture gate reviews require observability standards including structured logs, metrics, traces, health endpoints, and alerting configurations to ensure operational readiness and reliable monitoring.

Yes, the architecture review applies across code, infrastructure, and data flows, validating integration patterns like outbox and idempotence alongside operational requirements for comprehensive bounded-context changes.