Engineering notes
How we think, starting from real problems. Each note starts from a general question, explains the decision and points to the case where we applied it.
Rewrite a legacy system or migrate it by domain?
A twenty-year-old system still runs the operation. Do you throw it away and rebuild, or take it apart one piece at a time?
Where we applied it: A network of private outpatient clinics
02How to move from REST to GraphQL without rewriting the frontend
Dozens of services change their contract. Does the frontend that uses them have to change on the same day?
Where we applied it: A network of private outpatient clinics
03Entering an ecosystem of forty microservices
The service count says little. What actually matters when you enter a system of this size?
Where we applied it: A consumer platform with payments and subscriptions
04When a remote call should become a local rule
A calculation calls another service fourteen times for one answer. Is the problem the network or the design?
Where we applied it: A consumer platform with payments and subscriptions
05A switch for every fragile integration
The ERP is changing and the onboarding flow writes into it. Does everything stop until it is ready?
Where we applied it: A network of private outpatient clinics
Describe the system. We'll tell you what we see.
Ten minutes, one question at a time. At the end, our honest read of the case. It's the filter, before the call.