Aug – Oct 2026client work

Gamma Academy

I build real products, not just deploymentsFour consoles 110 agencies one database—no mess of multiple apps or logins

problem

The challenge: building a platform that works for many partners without copying or remaking apps for each one

I focused on multi-tenant solutions to keep things simple and reusable

Modular monolith with strict module boundaries over microservices.
tradeoffNo independent scaling of individual domains.
outcomeOne deployable, one database, no distributed-transaction fallout across identity, registration, agences, and challenges modules.
Schema-level tenancy: a Partenaire table and a required partenaireId FK on every tenant-owned model.
tradeoffEvery tenant query gets an extra indexed condition and a migration cost when the model set changes.
outcomeOnboarding the next partner is a database row plus a config entry. No new deployments.
Resolve tenant from the JWT payload, never the URL.
tradeoffExtra auth coupling in the default grant.
outcomeA mismatch between the session user and the URL slug is rejected instead of leaking cross-tenant data in the wrong surface.
Run staging and production as separate stacks on one droplet behind one wildcard DNS record.
tradeoffDisk and compute contention on shared nodes until load justifies a split.
outcomeDeploys, sonar reports, and staging verifications stay cheap and reproducible with the migration path (managed Postgres, per-partner droplets) kept open.