Case studies
Each case documents the constraint, the decision, the discarded alternative, and the measured outcome. It also states when to revisit the decision.
-
Infosistemas: a failure contract for RabbitMQ messaging
Intermittent failures between microservices with no contract for retry, DLQ, or duplication. Adding more consumers only pushed the overload elsewhere.
~98% fewer intermittent failures in critical flows
Open the case — Infosistemas: a failure contract for RabbitMQ messaging
-
VBET: analytics on top of a SQL Server we could not change
The database belonged to another team. The dashboard had to stop depending on a schema we did not control.
~7 min → <1 s commissions, from the original load to the warm cache
Open the case — VBET: analytics on top of a SQL Server we could not change
-
Flapper: discovering the domain before splitting the monolith
The product could not stop, and the original authors were already gone. Before migrating, we had to discover which boundaries the database still revealed.
~25% fewer tables in the domain-based split
Open the case — Flapper: discovering the domain before splitting the monolith