Case #001
PUMA LATAM — Serverless Backend
The PUMA LATAM case: serverless backend in Go on GCP, migrating from Pluggto to AnyMarket. Nacho had already worked for PUMA in 2025 — and a year and a…
Technologies
- GO
- GCP
- DOCKER
- GIT
PUMA
LATAM backend · Go · serverless · Crombie
Serverless backend for PUMA LATAM (Brazil) at Crombie: Cloud Functions in Go on GCP, migrating the flow from Pluggto to AnyMarket. Hybrid role: service desk, order reprocessing and bug fixing in parallel with the migration. The story starts earlier: in 2025 I was on PUMA Global Oceania (Next.js + GraphQL on GCP), the project fell through at board level — and a year and a half later they called me back.
ARCHITECTURE
Cloud Functions · Go · GCP serverless
The system: Cloud Functions in Go deployed on GCP, no frontend of our own — the store lives in Salesforce and we receive its data, or Pluggto's, and process it. The AnyMarket migration replaces Pluggto as the integrator. Fine detail under NDA.
push to dev to test → chaos
Discarded path
Discarded path: with just two branches (dev and main), using dev as a test bed meant pushing unverified code, triggering Terraform deploys and touching real GCP instances just to check a change. Expensive, slow and risky.
the client
PUMA LATAM (Brazil): sportswear e-commerce at regional scale. Working for a brand of this caliber demands real production standards — observability, code review, and zero room for 'I'll fix it later'.
local emulation Floci + Docker + logs dashboard
My initiative: I built a local emulation environment with Floci (GCP) and Docker, with a visual dashboard of all active logs. A sandbox to anticipate behavior without compromising the main environments — devs test locally before reaching dev. Higher-quality tests reach dev, and a critical branch stops being the test bed.
the consultancy
Crombie: the consultancy behind the project. The client renews with Crombie because we document and explain everything so anyone — even without a technical background — can understand it. That clarity is why I was chosen for this role.
SECURITY FIXES
beyond our scope
We're not the project architects and security isn't in our scope, but we analyze vulnerable packages and fix them bit by bit. Seniority is also minding what isn't yours when you know it's broken.
STACK
Cloud Functions in Go on GCP, Docker for local emulation, Git as the backbone of the workflow. Serverless to scale without a server to babysit.
CROMBIE RENEWS WITH PUMA FOR ITS CLARITY
Docs anyone can understand
The result: the client keeps choosing Crombie. What sells isn't just code — it's communication. Everything we do is documented and explained for anyone, even non-technical people, and I was picked for this role precisely because I can explain the complex with clarity and patience.
Let's talk? I'm open to projects and opportunities.