Architectural Analysis
New in v2.0 — Architectural Analysis has been completely rebuilt with improved detection and insights.
Mesrai’s Architectural Analysis helps you maintain clean, scalable code architecture by detecting anti-patterns and providing design recommendations.
Overview
Architectural Analysis goes beyond line-by-line code review to evaluate:
- Layer violations — Ensuring proper separation of concerns
- Circular dependencies — Detecting and preventing dependency cycles
- Coupling analysis — Identifying tightly coupled components
- Cohesion metrics — Ensuring modules have focused responsibilities
Key Features
Dependency Analysis
Mesrai analyzes your codebase to understand:
- How modules depend on each other
- Potential circular dependency issues
- Overly complex dependency chains
- Unused or redundant dependencies
Anti-Pattern Detection
Mesrai detects common architectural anti-patterns:
| Anti-Pattern | Description | Severity |
|---|---|---|
| God Class | Class with too many responsibilities | High |
| Circular Dependency | Modules that depend on each other | High |
| Feature Envy | Class using another class’s data excessively | Medium |
| Shotgun Surgery | Changes requiring many small edits | Medium |
| Long Parameter List | Functions with too many parameters | Low |
Layer Boundary Checks
Mesrai validates that your code follows proper architectural layers:
- Presentation layer shouldn’t directly access database
- Business logic should be separate from UI components
- Infrastructure code should be isolated
How It Works
Automatic Analysis
Architectural analysis runs automatically on every PR:
PR #123: Add user management feature
Architecture Analysis Results:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ No circular dependencies introduced
✅ Code follows established patterns
⚠️ Consider splitting UserService - it handles both auth and profileReview Comments
When architectural issues are found, Mesrai provides:
- Clear explanation of the issue
- Why it matters for maintainability
- Suggestions for improvement
- Links to best practices
Configuration
All settings are configured through the Mesrai Dashboard — no config files needed!
How to Configure
- Go to app.mesrai.com
- Select your Repository
- Navigate to Settings → Architecture
- Configure your preferences
Available Settings
| Setting | Description |
|---|---|
| Enable/Disable | Turn architectural analysis on or off |
| Strictness Level | How strict the analysis should be |
| Focus Areas | Which patterns to prioritize |
| Exclusions | Files or folders to skip |
Strictness Levels
| Level | Behavior |
|---|---|
| Strict | Flag all potential architectural issues |
| Moderate | Balance between thoroughness and noise |
| Relaxed | Focus on critical issues only |
What Gets Analyzed
Code Organization
- Module structure and boundaries
- File and folder organization
- Naming conventions
- Code grouping
Dependencies
- Import/export relationships
- Third-party library usage
- Internal module dependencies
- Circular reference detection
Design Patterns
- Proper use of design patterns
- SOLID principle adherence
- Clean architecture practices
- Separation of concerns
Best Practices
- Start with moderate settings — Begin with standard strictness and adjust based on your codebase
- Incremental adoption — Don’t try to fix all issues at once
- Review regularly — Check architectural insights periodically
- Team alignment — Ensure your team agrees on architectural standards
Metrics & Insights
Track architectural health over time in your dashboard:
- Dependency count — Total and per-module dependencies
- Issue trends — How architectural issues change over time
- Common patterns — Most frequent issues in your codebase
- Improvement tracking — Progress on fixing issues