
Arden Vela
New
From monolith to microservices: what I learned in 14 months
Our biggest mistake while splitting up the payment infrastructure was dividing services along “technical” boundaries. Good boundaries come from the business domain: payments, refunds and reconciliation were separate responsibilities managed by separate teams.
The second lesson was observability. Without distributed tracing, finding where a request slowed down could take weeks. Instrumenting first and decomposing second made life easier.
Third, and perhaps most importantly, we never deployed a migration without a rollback plan. At each step, the old and new paths ran side by side for a while. It sounds boring, but it is exactly what protects a good night of sleep.
There are still things to fix, but a 40% improvement in API response time and far fewer nighttime calls suggest we are on the right path.