Performance & data
We build and run the backend half of an ecommerce operation on Google Cloud — serverless containers on Cloud Run, images built by Cloud Build, credentials in Secret Manager, and every service holding an identity of its own.
Most of what an ecommerce business needs from a cloud is a handful of small services that answer HTTP, hold some state, talk to Shopify and to each other, and cost nothing when nobody is shopping. Cloud Run does exactly that, and it does it without asking you to run a cluster.
What separates a Cloud Run project that ages well from one that becomes somebody's problem is the boring layer: a reproducible build, an artifact you can point at, secrets that are not in the repo, a service account per service rather than one owner key, and a deploy you can undo. That is the layer we build.
Technologies
A Node.js service your Shopify theme or app calls, that needs to be fast, cheap at idle and safe to deploy on a Friday.
Imports, exports, image processing and document uploads that belong in object storage and a job, not in a web request.
One backend serving more than one storefront, where per-store configuration and per-service identity both matter.
We decide what is one service and what is three, what needs state, and what can be a job rather than a permanently running process.
A Dockerfile, a Cloud Build trigger and an Artifact Registry repository, so a push becomes an image and an image becomes a revision.
Each service gets a service account and reads its configuration from Secret Manager. Nothing sensitive lives in the repository or in a deploy script.
Health checks, structured logs, revision-based rollback, and a written note of what each service is and who it talks to.
Real projects that used this capability. Every one shipped.
A Node.js and Express service layer sitting between more than one storefront and the systems behind them — Shopify APIs, Google APIs and the shared operations each store would otherwise reimplement.
A Node.js ecommerce API estate moved off Heroku dynos onto serverless containers on Google Cloud Run, with a reproducible build, managed secrets and an identity per service.
The backend behind a guided eyewear recommendation running on two storefronts at once: one recommendation service, one catalogue reader, and per-store configuration rather than two forks.
Tell us about your store and your goals. We'll come back with a clear, honest plan and a transparent quote.