Application Architecture

Architecture interviews ask you to choose boundaries that match team structure, deployment, and change rate—not to name the most fashionable style. Compare monolith, modular monolith, microservices, event-driven, serverless, and layered/hexagonal/clean/onion models by trade-off.

Also cover domain modeling (DDD basics), frontend architecture (FSD, components, design systems, BFF, micro-frontends), and explicit trade-offs (coupling, cohesion, deployment complexity, team boundaries, operational cost, migration).

On interviews: given constraints (team size, release cadence, domain complexity), defend one style and what you would defer.

Common pitfalls: microservices by default, ignoring operational cost, and architecture diagrams without data flow or failure modes.

Checklist:

• State constraints before picking a style.
• Name ownership and deployment boundaries.
• Explain migration path from current state.
• Tie architecture to observability and testing.