senior-architect

System architecture diagrams are generated in Mermaid, PlantUML, or ASCII formats to visualize system components and layers. This process allows you to map out project structures and generate component diagrams directly from your current project context.

Deciding between a monolith and microservices involves structured decision workflows that evaluate your system's specific needs. This approach provides technical decision-making guidance by analyzing existing project dependencies and evaluating scalability requirements.

Analyzing code dependencies identifies coupling issues and circular dependencies within your system architecture. This assessment detects architectural patterns and code smells to help you evaluate the health of your project's structure.

Tech stack evaluation and database selection are supported through dedicated decision workflows. These workflows guide you in choosing appropriate databases, patterns, and technology stacks while facilitating overall architecture assessment.

Architecture decision records (ADRs) are supported to facilitate technical decision-making during system design reviews. This feature helps document architectural choices, evaluate microservices, and plan for scalability within your project.

You should reconsider microservices architecture when dependency analysis reveals tight coupling or when your project scale does not justify the complexity. Architecture assessment tools help detect such code smells and guide you toward a monolith if it fits better.