Make complex systems easier to reason about—and safer to change.

I help teams turn difficult architecture and delivery problems into clear decisions, workable boundaries, and systems that can be operated in the real world.

Start a conversation →Read the Field Notes

Where I can help

Event-driven systems

Architecture and technical direction for CDC, Kafka, streaming, event transformation, and systems that move important data in near real time.

Java platform architecture

Practical guidance for Java, Spring Boot, and Quarkus systems—from modular boundaries and APIs to reliability, testing, and operational readiness.

Integration and modernization

A clear path through legacy integration, API governance, migration constraints, and the trade-offs between extending, replacing, and extracting systems.

Architecture decision support

Independent reviews, decision records, technical roadmaps, and hands-on problem solving when a difficult system or delivery decision needs experienced judgment.

How I work

Architecture is useful when it improves the decisions a team can make. I work from the constraints outward, keep trade-offs visible, and stay close enough to implementation to test whether the design survives contact with reality.

The goal is not a more impressive diagram. It is a system with boundaries people understand, failure modes they can operate, and a path to change.

Useful engagement shapes

→Architecture review or technical due diligence
→Short advisory engagement around a high-risk decision
→Embedded technical leadership for a modernization initiative
→Design and delivery support for a platform or integration capability

A good first conversation

Bring the decision that is proving difficult: a platform direction, an integration boundary, a modernization plan, or a system that has become harder to change than it should be. We can start with the context, constraints, and what a useful outcome would look like.

Get in touch →