Skip to content
ballmüllersolutions logo Send an email Call us

K4 Architect

Shape systems and justify them: DDD, ports and adapters, CQRS and event sourcing, distributed systems with Orleans and Azure architecture.

Join the waiting list

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

  1. 4.1

    Architecture as a decision

    quality goals, trade-offs, architecture decision records (ADRs), the C4 model, costs (FinOps)

    20 h
  2. 4.2

    Strategic DDD

    domain, bounded contexts, context maps, event storming

    25 h
  3. 4.3

    Tactical DDD, ports and adapters

    aggregates, value objects, domain events, rules in the domain model, dependencies pointing inward, the modular monolith

    30 h
  4. 4.4

    CQRS and event sourcing

    when it pays off and when it does not, projections, versioning events

    25 h
  5. 4.5

    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

    40 h
  6. 4.6

    Integration and consistency

    outbox and inbox, process managers, idempotency, “at least once” delivery

    20 h
  7. 4.7

    Azure architecture

    the Well-Architected Framework, networking, identity, high availability and disaster recovery, multi-tenancy (an instance per customer or shared), governance

    30 h
  8. 4.8

    Security as architecture

    zero trust, threat modeling, data protection by design (GDPR), least privilege for identities

    20 h
  9. 4.10

    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

    20 h
  10. 4.11

    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

    25 h
  11. 4.12

    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

    25 h
  12. 4.13

    Data architecture

    OLTP and OLAP, data warehouse and lakehouse with Microsoft Fabric, ETL and ELT, Spark in overview

    20 h
  13. 4.14

    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

    15 h
  14. 4.9

    Final project

    the Kladde multi-tenant, with architecture documentation and an architecture review against a checklist

    30 h

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.

The lessons are only in German for now.

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 lessons
  1. Lesson 1 · about 180 minutes

    Was Architektur ist

  2. Lesson 2 · about 240 minutes

    Qualitätsziele

  3. Lesson 3 · about 240 minutes

    Abwägungen und ADRs

  4. Lesson 4 · about 240 minutes

    Das C4-Modell

  5. Lesson 5 · about 180 minutes

    Kosten als Architekturmerkmal (FinOps)

4.2 Strategic DDD

Indicative: 25 hours · 6 lessons
  1. Lesson 6 · about 240 minutes

    Die Domäne verstehen

  2. Lesson 7 · about 300 minutes

    Event Storming: der große Überblick

  3. Lesson 8 · about 240 minutes

    Event Storming: Abläufe im Detail

  4. Lesson 9 · about 240 minutes

    Bounded Contexts finden

  5. Lesson 10 · about 240 minutes

    Context Maps

  6. Lesson 11 · about 120 minutes

    Wem die Daten gehören

4.3 Tactical DDD, ports and adapters

Indicative: 30 hours · 7 lessons
  1. Lesson 12 · about 240 minutes

    Entitäten und Value Objects

  2. Lesson 13 · about 300 minutes

    Aggregate und ihre Grenzen

  3. Lesson 14 · about 240 minutes

    Regeln gehören ins Domänenmodell

  4. Lesson 15 · about 240 minutes

    Domain Events

  5. Lesson 16 · about 240 minutes

    Ports and Adapters

  6. Lesson 17 · about 240 minutes

    Der modulare Monolith

  7. Lesson 18 · about 180 minutes

    Bestehenden Code umbauen

4.4 CQRS and event sourcing

Indicative: 25 hours · 6 lessons
  1. Lesson 19 · about 180 minutes

    Wann CQRS und Event Sourcing sich lohnen

  2. Lesson 20 · about 180 minutes

    CQRS ohne Event Sourcing

  3. Lesson 21 · about 240 minutes

    Ein Aggregat aus Ereignissen

  4. Lesson 22 · about 240 minutes

    Ein Event Store auf SQL Server

  5. Lesson 23 · about 240 minutes

    Projektionen und Lesemodelle

  6. Lesson 24 · about 240 minutes

    Ereignisse versionieren

4.5 Distributed systems with Orleans

Indicative: 40 hours · 10 lessons
  1. Lesson 25 · about 240 minutes

    Virtuelle Akteure

  2. Lesson 27 · about 240 minutes

    Zustand speichern

  3. Lesson 28 · about 240 minutes

    Serialisierung und Versionierung

  4. Lesson 29 · about 240 minutes

    Event Sourcing im Grain

  5. Lesson 30 · about 240 minutes

    Wachsende Zustände partitionieren

  6. Lesson 31 · about 180 minutes

    Timer und Reminder

  7. Lesson 32 · about 240 minutes

    Observer und Streams

  8. Lesson 33 · about 180 minutes

    Orleans testen

  9. Lesson 34 · about 180 minutes

    Cluster in Container Apps

4.6 Integration and consistency

Indicative: 20 hours · 5 lessons
  1. Lesson 35 · about 180 minutes

    „Mindestens einmal“ zugestellt

  2. Lesson 36 · about 240 minutes

    Outbox

  3. Lesson 37 · about 240 minutes

    Inbox und idempotente Empfänger

  4. Lesson 38 · about 240 minutes

    Prozessmanager

  5. Lesson 39 · about 180 minutes

    Integration nach außen

4.8 Security as architecture

Indicative: 20 hours · 5 lessons
  1. Lesson 40 · about 180 minutes

    Zero Trust für Architekten

  2. Lesson 41 · about 240 minutes

    Bedrohungsmodell mit STRIDE

  3. Lesson 42 · about 240 minutes

    Datenschutz durch Technikgestaltung

  4. Lesson 43 · about 180 minutes

    Löschen in einem System, das nichts vergisst

  5. Lesson 44 · about 240 minutes

    Geringste Rechte für Identitäten

4.7 Azure architecture

Indicative: 30 hours · 8 lessons
  1. Lesson 45 · about 180 minutes

    Das Well-Architected Framework

  2. Lesson 46 · about 240 minutes

    Netz

  3. Lesson 47 · about 180 minutes

    Identität: Menschen, Mandanten, Dienste

  4. Lesson 48 · about 180 minutes

    Hochverfügbarkeit

  5. Lesson 49 · about 240 minutes

    Notfall: RTO, RPO und die Probe

  6. Lesson 50 · about 300 minutes

    Mandantenfähigkeit

  7. Lesson 51 · about 180 minutes

    Governance und Kosten

  8. Lesson 52 · about 120 minutes

    AZ-305 abgleichen

4.9 Final project

Indicative: 30 hours · 7 lessons
  1. Lesson 53 · about 180 minutes

    Planen

  2. Lesson 54 · about 300 minutes

    Mandanten anlegen und auflösen

  3. Lesson 55 · about 300 minutes

    Isolation beweisen

  4. Lesson 56 · about 300 minutes

    Ausliefern und betreiben

  5. Lesson 57 · about 300 minutes

    Architekturdokumentation

  6. Lesson 58 · about 180 minutes

    Architektur-Review

  7. Lesson 59 · about 240 minutes

    Verteidigung vor zwei Prüfenden

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.

More about the Kladde

Certifications

An offer, never a requirement: these Microsoft exams fit this stage. You take them at Microsoft; we are not a Microsoft training partner.

Keep learning with Microsoft Learn

Microsoft's learning paths and documentation that go with this course.

All courses at a glance