Skip to main content

Architectural Styles for Software Architects

Architectural styles are reusable high-level structures for a system. Layered, hexagonal and clean architecture organise code around dependencies, monolith, modular monolith and microservices choose deployment boundaries, and event-driven and serverless styles change how components are triggered and scaled.

Stage: Patterns and Styles · Part of the Software Architect roadmap · Last reviewed 19 November 2026

What to learn in Architectural Styles

Architectural Styles interview questions

When would you choose a modular monolith over microservices?

When the team is small, the domain is still being learned, or operational maturity is low. A modular monolith keeps clear internal boundaries and a single deployment, avoiding network failures and distributed data costs, and can be split later.

What is hexagonal architecture?

Hexagonal architecture puts the business logic at the centre, exposes it through ports, and connects databases, UIs and external services through adapters. Dependencies point inwards, so the core can be tested and changed without infrastructure.

Where Architectural Styles fits in the Software Architect roadmap

Architectural Styles belongs to the Patterns and Styles stage (advanced level), which takes about 6 hours. Choose the right shape.

Back to the full Software Architect roadmap