Algorithm for choosing architecture (source https://www.youtube.com/watch?v=q3YQy1lJutw) sa

eng-v2.mermaid

eng.mermaid

Logic Citations.md

Logic Citations (English/Español)

• Initial State: The process starts with a Layered Monolith.

• Transaction Frequency: Strong and frequent transactions lead to Clean/Hexagonal architecture within the monolith.

• Maintainability Focus: Long-life products with a focus on tests and maintainability trigger team-size evaluations.

• Monolith Retention: If the product is not long-lived, the recommendation is to maintain the monolith.

• Team Capacity (Small): Teams of 5–12 engineers should use Clean/Hexagonal within the monolith.

• Modular Monolith: This is the default intermediate path when team or infrastructure criteria are not fully met.

• Scaling Rhythm: If a domain scales differently, it should be extracted individually.

• Infrastructure Requirements: Transitioning to microservices requires solid CI/CD, observability, and tracing.

• Team Capacity (Large): 12–15+ engineers or a need for independent releases triggers the move to microservices.

• Traffic Patterns: Irregular or global traffic suggests a Partial Serverless approach.

• Consistency Model: Accepting eventual consistency leads to EDA/CQRS , whereas rejecting it requires maintaining simple synchrony.

spa-v2.mermaid

spa.mermaid