Module 3 of 10

Architectural Styles

Lessons

About This Module

An architectural style is a broad way of organising a whole system: how it is split into parts, how those parts talk to each other, and where its data lives. Each style has its own strengths and weaknesses, so choosing one is really a decision about which quality attributes matter most for your project.

You'll start with the most common choice you will face, monolith versus microservices, and why a monolith is often the right place to begin. Then you'll see how common architecture styles and patterns are classified, and take a closer look at two important ones: event-driven architecture, where components communicate through events, and hexagonal architecture (ports and adapters), which keeps business logic separate from databases, frameworks, and APIs.

Next up is Design Principles & Patterns, where you'll move from the structure of the whole system to the design of the components inside it.

Lessons

4 videos
01

Monolithic vs Microservice Architecture: Which To Use and When?

The advantages and disadvantages of monoliths and microservices, how microservices communicate, and how to decide which one fits your project.

02

Classifying Architecture Patterns

Mark Richards describes some ways of classifying common architecture styles and patterns, and why that classification makes sense.

03

A Beginner's Guide to Event-Driven Architecture

A gentle introduction to event-driven architecture with real-world use cases and main concepts such as event notification, CQRS, and event sourcing.

04

Hexagonal Architecture with Alistair Cockburn

The creator of hexagonal architecture, more correctly called Ports & Adapters, explains its rules and structure.