pact-architecture-patterns

To create C4 diagrams for system architecture design, you can use templates for Level 1-3 system context, containers, and components, rendered via ASCII or Mermaid formats to visualize boundaries and interactions.

Software architecture anti-patterns are flawed structural design choices that hinder scalability and maintainability, which you can identify and refactor using specific architectural review guidance and detection rules.

Writing an Architecture Decision Record (ADR) for component design involves documenting your architectural decisions using reference templates that capture context, decisions, and consequences for governance.

Yes, you can apply architectural patterns to both monoliths and microservices, as pattern selection guidance covers structural and behavioral design across distributed and single-tier system boundaries.

The best way to select design patterns for API contracts is to evaluate creational, structural, and behavioral pattern references to determine the optimal fit for your component interactions and system boundaries.

You should not use specific architectural patterns when they conflict with your system boundaries or introduce unnecessary complexity, which you can detect using provided anti-pattern reference guidelines.