senior-architect

To generate an Architecture Decision Record for a monolith vs microservices choice, provide your project context to receive a structured evaluation documenting the architectural rationale and trade-offs. This formalizes system design decisions and dependency analysis.

The best way to visualize system design for a tech stack evaluation is generating architecture diagrams using Mermaid, PlantUML, or ASCII. These visualizations compare deployment patterns and communicate trade-offs during formal design reviews.

Yes, you can use this to compare database selection options and deployment patterns. It performs tech stack evaluation to compare databases and frameworks, guiding tool selection by documenting architectural rationale and analyzing dependencies.

To document architectural rationale and analyze dependencies for governance, you generate Architecture Decision Records to formalize decisions. This captures design decisions contextually, satisfying requirements for dependency analysis and tech stack documentation.

Yes, this approach supports generating diagrams in both Mermaid and PlantUML for ADRs. It produces architecture diagrams in Mermaid, PlantUML, or ASCII to visualize systems and communicate trade-offs during design reviews.