Technical leadership with a business edge.
Software architecture for products that need to move fast.
How I help
Losing direction
“We are building fast, but I cannot tell if we are going in the right direction.”
Scaling risk
“We need to scale and I don’t know if the architecture will hold.”
Non-technical decisions
“I am non-technical and I need to make decisions about a team or a provider.”
Independent technical review
“We need an independent technical opinion on what we are building.”
Hidden tech debt
“I don’t know if the product is accumulating tech debt.”
Rewrite or continue?
“Should we keep building on what we have or start over?”
My recommendations come from over two decades of building systems and living with the consequences of those decisions. Technical and commercial considerations shape each other from the start. How I think →
Selected work
Retail, backend modernization
Replacing a backend without stopping 2,600 stores
Replacing the backend without stopping 2,600+ stores and 9,500+ terminals. No downtime allowed. A wrong data migration would have been visible in every store the next morning. 141M+ documents, 1TB+ data. Throughput target exceeded by 79%, query time reduced 216x.
Luxury e-commerce
One architecture across three cities
Three cities, three teams, one architecture. Distributed teams in Berlin, Geneva, and Shanghai building a luxury brand's e-commerce platform for China. Localization in Chinese and compliance with Chinese authority security requirements. Architectural decisions coordinated across three time zones.
Mobility & traffic management
Traffic data with no single source of truth
Multiple national traffic sources, each with a different schema and update cycle. No single source of truth, and consumers relying on the output daily. 18 microservices on AWS, 10,000+ events/day, 99.9% uptime. Serving HERE, TomTom, Radio24. In production since 2017.
Public sector
Architecture while requirements were still moving
400K+ entities, 9M+ API calls/hour at peak. Requirements still forming while the architecture needed to proceed. Optimizing Redis to relieve database pressure and building a roadmap from monolith toward modular architecture.
Enterprise content
Headless CMS for Content as a Service
Persistence and API layer for Crownpeak headless CMS, built for a Content as a Service model used by hundreds of Crownpeak clients worldwide. One API contract, many clients depending on it.
Open source platform
Ten years of evolution without rewrite
RESTHeart: 10+ years in production, 2M+ downloads. Architecture that evolved without rewrite across many major versions and breaking upstream changes. Adopted by Unisys, Northrop Grumman, and Crownpeak.
A 30-minute call to understand your situation, surface the key technical decisions, and determine if I can help.