Topics
Architecture
All articles on Architecture, newest first.
Transparency: I have revised all articles afterwards with the help of AI and translated them from German with its help. The ideas, experience and positions are my own. The audio versions of the German originals are read by a synthetic voice.
MCP, HTTP, Webhooks and A2A Explained Simply
MCP, HTTP with OpenAPI, webhooks and A2A connect systems at different levels. What matters is which responsibility lies at each boundary.
A2A: When Agents Work Together
Agent Card, Message, Task and Artifact explained clearly: how A2A 1.0 connects independent agent systems, what sets the protocol apart from MCP and when delegating to an independent system pays off.
Hourly Is Not Real Time
A closed hourly report answers different questions than ongoing operational monitoring – and gets simpler as soon as time windows, delays and measurement gaps are modeled explicitly.
2026 3
2026 3
- Products Report Through Their APIProduct statistics stay understandable when every system aggregates its own data and offers it through a small HTTP contract with uniform time semantics.SoftwareArchitectureAPIDelivery
- MCP Security: Tools, Permissions and Approvals for AI AgentsHow to integrate MCP tools into applications safely: server-side permission checks, human approvals, protection against prompt injection and traceable calls.SoftwareAIArchitecture
- AI in the Enterprise: Faster Development Needs Different ProcessesAI shortens research, design and implementation. If handoffs, ticket hierarchies and approvals stay the same, the bottleneck just moves – so large companies have to rethink workflow and governance together.SoftwareAIArchitectureDelivery
2024 1
2023 1
2022 1
2021 4
2021 4
- Jamstack as an Architecture Style for Web ApplicationsJamstack describes an architecture style with a pre-rendered frontend and decoupled services. This post puts the original building blocks JavaScript, APIs and Markup into context as of 2021.SoftwareArchitecture
- When CQRS and Event Sourcing Are Too MuchFor most systems, CRUD is enough. CQRS and Event Sourcing only pay off under clear conditions – this article offers an honest decision guide instead of patterns for their own sake.SoftwareArchitecture
- Architecture Decision Records: Decisions You Will Still Understand in Two YearsWhy did we choose PostgreSQL back then and decide against the message bus? ADRs make the why durable as a versioned Markdown artifact – instead of letting it seep away in hallway talk.SoftwareArchitecture
- Event Sourcing: The Event Store as a LogbookEvent Sourcing doesn’t store the current state but the sequence of events as the source of truth: the event store as a logbook, the state as the result of a fold. Benefits, honest costs and how it differs from CQRS.SoftwareArchitecture
2020 5
2020 5
- Team Automation with GitHub ActionsWhy I run selected, recurring checks as workflows – and how you can tell whether the automation actually takes load off the team.SoftwareArchitecture
- Read Models from Events: Projections Instead of Accidental CachesA read model built from events is a deliberately maintained projection for concrete queries. Origin and rebuild set it apart from an accidentally grown cache, even if the technical view can look cache-like.SoftwareArchitecture
- Cloud Guardrails Instead of Cloud GatekeepingWhy central approval processes in the cloud breed shadow infrastructure and how technically enforced guardrails – SCPs, Permission Boundaries, Config Rules, budgets – give teams their freedom of movement back.SoftwareArchitecture
- Bounded Contexts Before the Service SplitBefore I split services, I clarify domain boundaries. A bounded context is a language boundary and a possible, but not mandatory, service split.SoftwareArchitecture
- The Aggregate as a Consistency BoundaryAn aggregate is neither an ORM entity nor a table but a consistency and transaction boundary: a cluster of objects that an Aggregate Root protects as a unit. Why a transaction changes exactly one aggregate and other aggregates are referenced only by ID.SoftwareArchitecture
2019 4
2019 4
- PouchDB and Offline-FirstIf you allow writes while offline, you move from request/response to replication – and the revision tree of PouchDB and CouchDB turns conflicts into a job for the domain model.SoftwareArchitecture
- Cleanly Separating Commands, Events and QueriesCommand, event and query are three kinds of messages with clear semantics: a request that can be rejected, a fact that has happened and a query without side effects. If you name and separate them cleanly, you gain clarity in the model – without a big CQRS setup.SoftwareArchitecture
- Secrets in the Build Are Product DecisionsSecrets in the build are a trust problem: who may see, store and deploy what, and when?SoftwareDevOpsArchitecture
- CQRS Is a Domain Boundary, Not a FrameworkCQRS separates the model for writing from the model for reading – a domain decision, not an installable framework. When the boundary pays off, how to start small and which mix-ups get expensive.SoftwareArchitecture
2017 2
2017 2
- PWA Weather: Offline Is a FeatureA small weather app built as a Progressive Web App shows why offline behavior is a product decision and how honestly a UI should deal with outdated data.SoftwareArchitecture
- HTML5, CSS3 and ECMAScript as a BaselineIn the spring of 2017, CSS Grid, Flexbox, fetch and native ES2015 carry so far that the first architecture question in the frontend deserves to be asked again: How far do I get without a framework?SoftwareArchitecture
2015 2
2015 2
- Functional Styles in Everyday CodeWhy functional style in everyday team work in 2015 does not mean Haskell, but the discipline of separating pure functions from I/O – and how ES2015 finally makes that convenient.SoftwareArchitecture
- Programming Styles as an Architecture ComparisonThe same small task solved in dozens of programming styles is the most compact architecture comparison I know – because every style is a deliberately chosen set of constraints.SoftwareArchitecture
2014 3
2014 3
- MathParser: Parsers as a Thinking ToolA look back at a parser demo of my own from 2010 shows why a handwritten expression parser teaches more about layers, structure and the boundary between syntax and semantics in a few lines than many a large project.SoftwareArchitecture
- HTTP APIs: Small, Stable, ReadableWhat the Heroku HTTP API Design Guide is worth when you hold it up against your own APIs – and why a few resources, a versioning promise and self-explanatory errors achieve more than any framework.SoftwareArchitecture
- What I Was Looking for in ElixirIt wasn’t the syntax that brought me to Elixir but the execution model of the Erlang VM – processes, messages and supervisors, seen through JavaScript and C# eyes.SoftwareArchitecture