Software Architecture & Engineering

Enough engineering depth to know whether the architecture is implementable.

3Questions
17Flashcards
19Terms
2/20Topics covered
The syllabus

20 topics in this area.

Each topic is the unit content is filed against. Topics with nothing in them yet are shown too — they are the honest edge of the curriculum rather than a gap being hidden.

Software Architecture

General material on the engineering underneath an architecture.

3 quiz 16 cards 18 terms

SOLID

Five design principles, two of which scale beyond the class.

No content yet

Domain-Driven Design

Ubiquitous language, bounded contexts and context mapping.

No content yet

Bounded Contexts

Where one model ends and another begins, and why forcing one fails.

No content yet

Clean Architecture

Concentric layers with dependencies pointing only inwards.

No content yet

Hexagonal Architecture

Ports defined by the domain, adapters supplied by infrastructure.

No content yet

Microservices

Independent deployability, and the distributed problems it buys.

No content yet

Modular Monolith

Enforced internal boundaries without a network between them.

No content yet

Service Boundaries

Drawing lines along change patterns rather than technical layers.

No content yet

Design Patterns

Reusable solutions at code level, and when they become ceremony.

No content yet

Refactoring

Changing structure without changing behaviour, in verified steps.

No content yet

Technical Debt

Deliberate, tracked and repaid — as distinct from mess.

No content yet

Testing Strategies

The pyramid, and the contract tests distributed systems add to it.

No content yet

Contract Tests

Capturing what consumers actually use, not what the API documents.

No content yet

CI/CD

Continuous integration and delivery, and the architecture that caps them.

No content yet

Release Strategies

Blue-green, canary, shadow and progressive delivery.

1 cards 1 terms

Feature Flags

Decoupling deploy from release, with an expiry date.

No content yet

Trunk-Based Development

Short-lived branches, and unmerged work as inventory.

No content yet

Code Review

Where architectural rules are enforced by people rather than by tools.

No content yet

DORA Metrics

Throughput and stability moving together rather than trading off.

No content yet