Retail · department store · 2023 — 2024
A purchase history spread across seven systems
A Redis cache layer in front of seven systems, refreshed in the background through SNS and SQS, so the purchase history waits on none of them.
Work
Client cases, by kind of problem. Each one with its architecture diagram.
Connecting systems that already exist
When the data you need lives in systems you can't change.
Retail · supermarkets in two countries · 2020 — 2021
Making the website's stock match the store's
Five microservices connected through Pub/Sub that carry stock from the merchandising system to the e‑commerce site, in two countries.
Decoupling with events
When one piece shouldn't wait on another to do its job.
Entertainment · cinema chain · 2024 — 2025
Email notifications that don't fall over under load
An email flow split into two services connected through Azure Service Bus, so the call to SendGrid doesn't drag the rest down.
Changing the UI from the backend
When every screen change depends on shipping an app.
Retail · two supermarket chains · 2022 — 2024
Changing an app's screens without shipping a new version
A BFF that sends the whole screen —content, styles and actions— so Android, iOS and the web change without shipping a new version.