Skip to content
Frontend Architecture Patterns

How to Choose a Pattern

Choosing the right architecture depends on your specific context. This guide explains how to use our documentation and tool to make an informed decision.

1. Define Your Constraints

Section titled “1. Define Your Constraints”

Before looking at patterns, identify your non-negotiables:

  • Does the site need to be SEO-friendly?
  • How many teams will be working on it?
  • Is offline support required?

2. Evaluate Interactivity

Section titled “2. Evaluate Interactivity”

Determine if your application is “document-like” (MPA) or “app-like” (SPA). For something in between, consider Islands or SSR/Hybrid.

3. Consider Organizational Scaling

Section titled “3. Consider Organizational Scaling”

If you have 10+ teams working on a single product, Micro Frontends might be worth the complexity. For smaller teams, a Modular Monolith is usually better.

4. Use the Selector Tool

Section titled “4. Use the Selector Tool”

Our rule-based engine automates this scoring process for you. Try the Pattern Selector to get a personalized recommendation based on your project’s requirements.