Topic 01 / 08 · 09 articles

Cloud Architecture

About this topic

152 words

Most cloud architecture advice is written for companies with a platform team and a generous budget. The articles here are written for the opposite situation: a small team, a real product, and a bill that has to make sense every month.

I focus on Google Cloud because it is where I run production systems, but the reasoning travels. Each piece starts from a concrete constraint — a latency target, a traffic shape, a cost ceiling — and works through the options until one of them is clearly the right trade-off. You will find serverless compute and its cold starts, scale-to-zero as a deliberate budget strategy, media delivery through CDNs, event-driven designs, and the hidden fixed costs that make a “free tier” architecture surprisingly expensive.

Where numbers appear, they are either measured or clearly labelled as illustrative, and pricing always links to the official page so you can check it against today’s rates.

01Start here

Featured

A design review of a Google Cloud image pipeline: signed uploads, fixed variants, immutable names and a CDN, with failure and deletion paths worked through.

15 min

02All articles in Cloud Architecture

  • · 12 min

    Cloud Run jobs or services for batch work

    Batch work behaves badly behind an HTTP endpoint. Compare Cloud Run jobs and services on retries, parallelism and exit codes, and shard work across tasks.

  • · 9 min

    Reading a GCP bill like an architect

    Turn the Cloud Billing export into five queries that explain a Google Cloud invoice: what is fixed, what scales, what is a credit, and who owns each line.

  • · 16 min

    GDPR deletion is a distributed-systems problem

    An erasure request touches your database, search index, buckets, logs, analytics, backups and vendors. Here is how I make that deletion retryable and provable.

  • · 15 min

    Refresh-on-read instead of a cron job

    A scheduled sync pays to refresh every record, including the ones nobody reads. Refreshing stale data when someone looks makes cost follow attention.

  • · 15 min

    Cloud Run cold starts: a field guide

    Measure which phase of a Cloud Run cold start is slow, match it to the lever that shortens it, and pay for warm instances only where the latency earns it.

  • · 15 min

    Serving user images without burning money

    A design review of a Google Cloud image pipeline: signed uploads, fixed variants, immutable names and a CDN, with failure and deletion paths worked through.