All topics
Architecture

Architecture as the art of trade-offs, decided with the system in mind.

7 articlesEN · DE

Architecture is not diagrams — it is the small set of decisions that are expensive to reverse, made well. Service boundaries, where state lives, how components fail and recover: get these right and a system stays cheap to change for years. Across 12+ years building platforms at scale, I have learned good architecture is mostly owning trade-offs honestly, not chasing the newest pattern.

Articles in this hub

7 articles
  • Domain-Driven Design in 2026: A Practical GuideAdvanced
    Aug 1, 202611 min

    Domain-Driven Design in 2026: A Practical Guide

    Domain-Driven Design is not a folder structure or a bag of patterns. It's a way to align software with the business. A practical 2026 guide: strategic vs tactical DDD, bounded contexts, aggregates, when it's worth it, and how to start — no jargon.

    Read article
  • Monolith vs Microservices in 2026: The Honest Trade-offsIntermediate
    Jul 31, 20266 min

    Monolith vs Microservices in 2026: The Honest Trade-offs

    Neither a monolith nor microservices is 'modern' or 'legacy'. Each trades one kind of complexity for another. An honest 2026 guide: the real trade-offs, where each wins, the anti-patterns, and a decision framework — no dogma.

    Read article
  • The CAP Theorem, Honestly: What It Really Means When You Pick a DatabaseIntermediate
    Jul 28, 20267 min

    The CAP Theorem, Honestly: What It Really Means When You Pick a Database

    The CAP theorem is not 'pick two of three.' Partitions aren't optional, so the real choice is consistency vs availability during a network split — plus PACELC for the 99% of the time nothing is broken. A practical guide to choosing a database.

    Read article
  • How to Send 1,000,000 Notifications Without Falling OverIntermediate
    Jul 13, 20268 min

    How to Send 1,000,000 Notifications Without Falling Over

    A vendor-neutral system-design walkthrough of the message-queue architecture that sends a million notifications without taking your API down: fan-out workers, back-pressure, retries, and dead-letter queues.

    Read article
  • Sovereign by Design: Building a Sovereign Platform on KubernetesAdvanced
    Jul 12, 20267 min

    Sovereign by Design: Building a Sovereign Platform on Kubernetes

    A practical 2026 architecture for digital sovereignty: treat sovereign cloud as three layers — data, operational, technical — and use Kubernetes, external key custody, and a real exit path to make sovereignty a design property instead of a marketing sticker.

    Read article
  • Secure-by-Default GKE: A Reference Architecture for 2026Advanced
    Jul 5, 20267 min

    Secure-by-Default GKE: A Reference Architecture for 2026

    A practical secure-by-default GKE reference architecture for 2026: defense in depth across identity, network, supply chain, admission, runtime, and observability — with Workload Identity Federation and Binary Authorization at the core.

    Read article
  • Pub/Sub or Eventarc? Event-Driven GCP Without the SpaghettiAdvanced
    Jun 29, 20265 min

    Pub/Sub or Eventarc? Event-Driven GCP Without the Spaghetti

    When to reach for Pub/Sub, when for Eventarc, and how to keep an event-driven GCP system clean: idempotency, dead-letter queues, and the trap of fan-out spaghetti.

    Read article

FAQ

What is your architecture background?
12+ years designing and operating platforms at scale in large enterprise environments, as a Google Cloud Ambassador, 5× Google Cloud Professional certified. I get the hard, hard-to-reverse decisions right so the system stays cheap to change for years.
Are you available to hire?
Yes — system design, service boundaries, event-driven architecture and scalability reviews, as a contract, consulting or selected full-time engagement, remote across the EU or on-site in Germany. I work fluently in English.
How do we start working together?
Tell me about the system you are designing or struggling to change on the contact page, and I will reply with how I can help.

Designing a system you have to live with?

From service boundaries to event-driven design and resilience, I help teams make the expensive-to-reverse decisions well — and keep the architecture cheap to change.

See architecture services →
ENDE