Insights
Notes from the work
Practical engineering write-ups, drawn from the systems we have built ourselves. We say what we did, why, and what it costs.
Architecture
2 min read
Send the message only after the save: reliable events between services
Why a message sent inside a database transaction can tell a lie, and the simple pattern that stops a rollback leaving a ghost message behind.
Security
2 min read
Services that prove who they are: mutual TLS between microservices
How callers are checked twice inside our platform, what it takes to run, and the honest cost of doing it properly.
API design
2 min read
Write the API contract first, and let the build guard it
How one written contract keeps services, the backend-for-frontend and the apps in step, and why a phone makes breaking changes expensive.
Operations
2 min read
Where should a setting live? The config server or the jar
A simple way to sort every setting into one home, and a precedence surprise that silently switched off our metrics.
Matching
2 min read
A match only counts when both say yes: scoring from both sides
Why one-sided recommendations waste people's time, how we combine two scores into one, and how we keep newer profiles from disappearing.
Facing one of these problems?
Tell us what you are working on. We will reply with an honest view.