K4 Architect
Shape systems and justify them: DDD, ports and adapters, CQRS and event sourcing, distributed systems with Orleans and Azure architecture.
Who it is for
For experienced developers who want to make and justify architecture decisions. A course makes nobody an architect – which is why this stage requires professional experience.
Prerequisites
K3 and at least a year of professional experience, or two years of professional experience and the placement test.
Afterward, you can
- Make architecture decisions, weigh them and record them as ADRs
- Shape systems into bounded contexts with domain-driven design
- Keep domain rules in the domain model, with ports and adapters
- Decide when CQRS and event sourcing pay off
- Build and run distributed systems with Orleans
- Secure consistency across system boundaries with outbox, inbox and idempotency
- Design Azure architectures to the Well-Architected Framework, multi-tenant ones included
- Build security and data protection into the architecture from the start
- Compare code architecture styles and justify the one that fits
- Weigh a modular monolith, microservices and virtual actors against each other
- Design data for analytics with a warehouse and a lakehouse
- Represent architecture in a team, estimate and explain it
Contents
- 4.1
20 h
Architecture as a decision
quality goals, trade-offs, architecture decision records (ADRs), the C4 model, costs (FinOps)
- 4.2
25 h
Strategic DDD
domain, bounded contexts, context maps, event storming
- 4.3
30 h
Tactical DDD, ports and adapters
aggregates, value objects, domain events, rules in the domain model, dependencies pointing inward, the modular monolith
- 4.4
25 h
CQRS and event sourcing
when it pays off and when it does not, projections, versioning events
- 4.5
40 h
Distributed systems with Orleans
virtual actors, the grain as an aggregate's consistency boundary, persistence and serialization with versioning, partitioning growing state, observers and streams, clusters in Container Apps
- 4.6
20 h
Integration and consistency
outbox and inbox, process managers, idempotency, “at least once” delivery
- 4.7
30 h
Azure architecture
the Well-Architected Framework, networking, identity, high availability and disaster recovery, multi-tenancy (an instance per customer or shared), governance
- 4.8
20 h
Security as architecture
zero trust, threat modeling, data protection by design (GDPR), least privilege for identities
- 4.10
20 h
Code architecture: layers, onion, hexagonal, clean, vertical slice
the same small feature built in each style, what each protects against and what it costs, architecture tests, how it relates to the ports and adapters of 4.3
- 4.11
25 h
Architecture styles and distributed systems in breadth
layers, microservices versus a modular monolith, event-driven, serverless, SOA as history, CAP and PACELC, consistency models, cloud design patterns, micro-frontends, strangler fig and anti-corruption layer, fitness functions
- 4.12
25 h
Microservices in practice
service boundaries, synchronous and asynchronous, data per service, sagas, an API gateway with YARP, Dapr on Container Apps, observability across services, microservices or Orleans
- 4.13
20 h
Data architecture
OLTP and OLAP, data warehouse and lakehouse with Microsoft Fabric, ETL and ELT, Spark in overview
- 4.14
15 h
The architect in the team
communication and stakeholders, estimating, presenting and defending decisions, mentoring, Scrum and Kanban, enterprise architecture with TOGAF and ArchiMate in overview
- 4.9
30 h
Final project
the Kladde multi-tenant, with architecture documentation and an architecture review against a checklist
About 345 hours in all (indicative).
Lessons
You see the text and video of every lesson here on the site after buying the course; the titles and goals are already shown. A self-study course: you work through the lessons in order and check your exercises yourself against the solutions.
You can read the first module (4.1) for free, with text and video, without signing in: so you see how the course works before you buy.
The lessons stand under their modules, in the order of the course. Click a module to open or close its lessons.
4.1 Architecture as a decision
Indicative: 20 hours · 5 lessonsfree to read
Lesson 1 · about 180 minutes
What architecture is
Lesson 2 · about 240 minutes
Quality goals
Lesson 3 · about 240 minutes
Trade-offs and ADRs
Lesson 4 · about 240 minutes
The C4 model
Lesson 5 · about 180 minutes
Cost as an architecture characteristic (FinOps)
4.2 Strategic DDD
Indicative: 25 hours · 6 lessons
Lesson 6 · about 240 minutes
Understanding the domain
Lesson 7 · about 300 minutes
Event storming: the big picture
Lesson 8 · about 240 minutes
Event storming: processes in detail
Lesson 9 · about 240 minutes
Finding bounded contexts
Lesson 10 · about 240 minutes
Context maps
Lesson 11 · about 120 minutes
Who owns the data
4.3 Tactical DDD, ports and adapters
Indicative: 30 hours · 7 lessons
Lesson 12 · about 240 minutes
Entities and value objects
Lesson 13 · about 300 minutes
Aggregates and their boundaries
Lesson 14 · about 240 minutes
Rules belong in the domain model
Lesson 15 · about 240 minutes
Domain events
Lesson 16 · about 240 minutes
Ports and adapters
Lesson 17 · about 240 minutes
The modular monolith
Lesson 18 · about 180 minutes
Restructuring existing code
4.4 CQRS and event sourcing
Indicative: 25 hours · 6 lessons
Lesson 19 · about 180 minutes
When CQRS and event sourcing pay off
Lesson 20 · about 180 minutes
CQRS without event sourcing
Lesson 21 · about 240 minutes
An aggregate from events
Lesson 22 · about 240 minutes
An event store on SQL Server
Lesson 23 · about 240 minutes
Projections and read models
Lesson 24 · about 240 minutes
Versioning events
4.5 Distributed systems with Orleans
Indicative: 40 hours · 10 lessons
Lesson 25 · about 240 minutes
Virtual actors
Lesson 26 · about 300 minutes
The grain as an aggregate’s consistency boundary
Lesson 27 · about 240 minutes
Storing state
Lesson 28 · about 240 minutes
Serialization and versioning
Lesson 29 · about 240 minutes
Event sourcing in the grain
Lesson 30 · about 240 minutes
Partitioning growing state
Lesson 31 · about 180 minutes
Timers and reminders
Lesson 32 · about 240 minutes
Observers and streams
Lesson 33 · about 180 minutes
Testing Orleans
Lesson 34 · about 180 minutes
Clusters in Container Apps
4.6 Integration and consistency
Indicative: 20 hours · 5 lessons
Lesson 35 · about 180 minutes
“At least once” delivery
Lesson 36 · about 240 minutes
Outbox
Lesson 37 · about 240 minutes
Inbox and idempotent receivers
Lesson 38 · about 240 minutes
Process manager
Lesson 39 · about 180 minutes
Integration with the outside world
4.8 Security as architecture
Indicative: 20 hours · 5 lessons
Lesson 40 · about 180 minutes
Zero trust for architects
Lesson 41 · about 240 minutes
Threat modeling with STRIDE
Lesson 42 · about 240 minutes
Data protection by design
Lesson 43 · about 180 minutes
Deleting in a system that forgets nothing
Lesson 44 · about 240 minutes
Least privilege for identities
4.7 Azure architecture
Indicative: 30 hours · 8 lessons
Lesson 45 · about 180 minutes
The Well-Architected Framework
Lesson 46 · about 240 minutes
Networking
Lesson 47 · about 180 minutes
Identity: people, tenants, services
Lesson 48 · about 180 minutes
High availability
Lesson 49 · about 240 minutes
Disaster recovery: RTO, RPO and the drill
Lesson 50 · about 300 minutes
Multi-tenancy
Lesson 51 · about 180 minutes
Governance and cost
Lesson 52 · about 120 minutes
Matching AZ-305
4.10 Code architecture: layers, onion, hexagonal, clean, vertical slice
Indicative: 20 hours · 6 lessons
Lesson 53 · about 180 minutes
What code architecture protects against
Lesson 54 · about 180 minutes
Classic layers
Lesson 55 · about 240 minutes
Onion and clean architecture
Lesson 56 · about 120 minutes
Hexagonal compared
Lesson 57 · about 240 minutes
Vertical slice
Lesson 58 · about 120 minutes
Comparison, architecture tests and decision
4.11 Architecture styles and distributed systems in breadth
Indicative: 25 hours · 8 lessons
Lesson 59 · about 180 minutes
Architecture styles at a glance
Lesson 60 · about 180 minutes
Modular monolith versus microservices
Lesson 61 · about 180 minutes
Event-driven and serverless as architecture
Lesson 62 · about 240 minutes
CAP, PACELC and consistency models
Lesson 63 · about 240 minutes
Cloud design patterns
Lesson 64 · about 180 minutes
Replacing instead of rewriting
Lesson 65 · about 120 minutes
Micro-frontends in outline
Lesson 66 · about 120 minutes
Keeping architecture checkable: fitness functions
4.12 Microservices in practice
Indicative: 25 hours · 8 lessons
Lesson 67 · about 180 minutes
Service boundaries
Lesson 68 · about 180 minutes
Communicating synchronously and asynchronously
Lesson 69 · about 180 minutes
Data per service
Lesson 70 · about 240 minutes
Sagas across services
Lesson 71 · about 180 minutes
An API gateway with YARP
Lesson 72 · about 240 minutes
Dapr on Container Apps
Lesson 73 · about 120 minutes
Observing across services
Lesson 74 · about 120 minutes
Microservices or virtual actors?
4.13 Data architecture
Indicative: 20 hours · 5 lessons
Lesson 75 · about 180 minutes
OLTP and OLAP
Lesson 76 · about 240 minutes
Data warehouse and lakehouse with Microsoft Fabric
Lesson 77 · about 240 minutes
ETL and ELT
Lesson 78 · about 180 minutes
Spark in overview
Lesson 79 · about 240 minutes
Data as an architecture decision
4.14 The architect in the team
Indicative: 15 hours · 6 lessons
Lesson 80 · about 180 minutes
Communicating and stakeholders
Lesson 81 · about 180 minutes
Estimating and dealing with uncertainty
Lesson 82 · about 180 minutes
Presenting and defending decisions
Lesson 83 · about 120 minutes
Mentoring and architecture reviews
Lesson 84 · about 120 minutes
Scrum and Kanban
Lesson 85 · about 60 minutes
Enterprise architecture in overview
4.9 Final project
Indicative: 30 hours · 7 lessons
Lesson 86 · about 180 minutes
Planning
Lesson 87 · about 300 minutes
Creating and dissolving tenants
Lesson 88 · about 300 minutes
Proving isolation
Lesson 89 · about 300 minutes
Delivering and operating
Lesson 90 · about 300 minutes
Architecture documentation
Lesson 91 · about 180 minutes
Architecture review
Lesson 92 · about 240 minutes
Architecture review with a checklist
Final project: the Kladde
What the Kladde can do after this course
Rebuilt into domain modules: quotes and appointments as aggregates in Orleans grains, the sales pipeline with event sourcing and read models, multi-tenant (an instance per customer or shared, justified in an architecture decision), with a C4 model and a cost calculation.
At the end you present your architecture and its documentation and check both against a checklist of the questions an architecture review asks – on your own or with colleagues.
Certifications
An offer, never a requirement: these Microsoft exams fit this stage. You take them at Microsoft; we are not a Microsoft training partner.
AZ-305 Azure Solutions Architect Expert
Requires AZ-104.
Keep learning with Microsoft Learn
Microsoft's learning paths and documentation that go with this course.