Thomas Bouzy

Context

Fan-token wallets moved real money and real assets. The existing state-based model made it impossible to answer "how did this balance get here?" — a hard problem when finance, support and regulators all ask that question.

Approach

Introduced Event Sourcing on the transaction flows with an outbox pattern over SNS/SQS, so every balance change is a stored, replayable fact rather than an overwritten row. Projections rebuild read models from the log.

Result

1,000+ financial transactions a minute with a complete audit trail, reconciliation that stopped being archaeology, and bug investigations that replay instead of guess.

Context

Engagement features — challenges, points, leaderboards — had to feel instant for a global audience, and the load arrives in spikes, not curves.

Approach

Major contributor on an event-driven gamification engine consuming the platform's activity stream, with Redis-backed leaderboards and idempotent handlers so replays never double-score.

Result

Sustained 30,000 events per minute with live leaderboard updates, and a scoring model product could extend without engineering rework.

Context

A digital agency serving large enterprise accounts on a legacy codebase that couldn't keep up with what clients now needed from their data.

Approach

Led an incremental migration to a modern API architecture on Symfony and API Platform — strangler-style, feature by feature, so client work never stopped. Rebuilt the CI/CD pipelines alongside it.

Result

A maintainable API layer serving enterprise accounts, faster deploys, and four junior developers who came out of it able to own features themselves.

Context

A volunteer team shipping fast across a three-app monorepo — a public site, a shop taking real payments, a back-office. No automated tests anywhere, a CI that only checked the build, and no map of what that was costing.

Approach

Read-only first, fixing nothing: four prioritised reports — 17 security findings, 11 on quality and debt, 6 on deployment weight, and an SEO audit scoring 56/100 across 34 findings — each item written as a card the team could pick up, with severity, effort and acceptance criteria. Then I took the critical ones myself.

Result

A free-cart path that trusted the client is now revalidated server-side, editorial content injected into structured data is escaped, security headers are global, and both the CI actions and the base image are pinned. The platform went from zero automated tests to covering its payment flows and admin authentication, with CodeQL in the pipeline.

Context

Building a département's association directory is done by hand today — commune by commune, copy-pasted from town-hall sites. Slow, not reproducible, and nobody can say where any given line came from.

Approach

An eight-stage cost funnel over open data (the RNA and the government directory), enriched by crawling the public sources of the collectivités themselves, with the provenance of every value kept beside it. Local-first by design: one process, one SQLite file, an interface on localhost — requests leave the user's machine, never mine.

Result

On Ille-et-Vilaine: 332 of 353 communes resolved and 31,273 associations in 40 seconds, then 36,170 classified and 748 mail domains verified in four. A measured pre-filter cut the volume that would need inference from 40.3% to 6.5% — the target was 20% — without dropping one page that had produced a contact, and before a line of inference existed.