Migrating 7.5M production users and enabling SSO
Moving millions. Keeping identity connected.
A production-user migration, a new database, and a more connected sign-in experience across global markets.
Read case studyI build distributed systems, lead production migrations, and help engineers understand the choices behind them.
About the engineerCase studies
Production migrations, automated workflows, and performance engineering.
Moving millions. Keeping identity connected.
A production-user migration, a new database, and a more connected sign-in experience across global markets.
Read case studyFrom an idea to a working system.
Building Media Planner from inception, connecting Java services and AWS workflows, and guiding the team along the way.
Read case studyA faster path between people and data.
Improving application performance with WebSocket connections, distributed caching, and carefully built Spring Boot APIs.
Read case studyTechnical articles & videos
Start with a database deep dive, a systems pattern, or a video explanation.
Browse all articles & videosWhat you’ll learnFollow how a database recovers committed changes using its log.
Watch video (opens in a new tab)What you’ll learnExplain ACID properties and the guarantees of database transactions.
Read article (opens in a new tab)What you’ll learnExplain how membership and failure information spread between nodes.
Read article (opens in a new tab)Engineering playground
Explore an illustrative request flow, then open the principles behind reliability, scale, and clarity.
A service should have an intentional failure boundary. Timeouts, bounded retries, and circuit breakers help prevent a local problem from becoming a wider outage. Observability should make that boundary visible.
At Capillary Technologies, the work included Resilience4j circuit breakers and a shared library for retry patterns on external API calls.
Separate work that needs an immediate answer from work that can wait. Queues and orchestration can make that separation explicit, but they also introduce delivery, ordering, and recovery decisions.
At CommerceIQ, Media Planner combined Java microservices with serverless workflows using AWS Lambda, SQS, S3, and Step Functions.
Make useful signals easy to find. Dashboards, explicit boundaries, and readable explanations help a team move from noticing a problem to understanding it. The people operating a system are part of its design.
At PayPal, the work included Grafana dashboards for chargeback tracking. Scale to Billions carries the same interest in explanation into articles and videos.
The people operating a system are part of its design.