sde-architecture

Service boundary analysis with bounded context map and migration sequence

Resilience pattern recommendations matched to identified failure modes with monitoring plan

Phased migration plan with rollback strategy, success criteria, and monitoring plan

Full Architecture Decision Record with alternatives, consequences, and review trigger

Architecture Decision Record: context, decision, consequences, alternatives considered, status lifecycle. Use when making a significant architectural decision that the team needs to understand and revisit.

Event sourcing, CQRS, outbox pattern, at-least-once vs exactly-once delivery, event schema design and versioning. Use when designing event-driven systems or evaluating whether to adopt event sourcing.

Safe migrations for DB/service/language/framework: strangler fig pattern, phased cutover, feature flags, rollback triggers and procedures. Use when planning a risky migration.

Logs/metrics/traces trinity, golden signals (latency/traffic/errors/saturation), SLO->SLI->SLA chain, alert fatigue prevention. Use when designing monitoring for a new service or fixing alerting that's too noisy.

Circuit breaker, bulkhead, timeout, retry with exponential backoff + jitter, fallback, health check patterns. Use when designing a service that calls external dependencies or when debugging cascading failures.

Monolith-to-microservices: identify seams by business capability and bounded contexts (DDD), event contracts, migration sequencing. Use when deciding whether and how to break up a monolith.

Classify debt using Fowler matrix (reckless/deliberate/inadvertent/prudent), payoff analysis, priority scoring, tracking strategy. Use when deciding what tech debt to pay off and in what order.