`Shopify` Replaces Redis Inventory Reservations With MySQL

// related

• #0001

  #0001Infra & SaaSGeekNews3 hours ago

  How Container Registries Work: Push/Pull Images Directly

  40radar

  Registry bugs often hide below the docker push surface. Understanding blobs, tags, manifests, and platform metadata helps debug broken deploys faster.

  • —A registry is a content-addressable blob store; layers are referenced by digest, so missing blobs break pulls even when tags look valid.
  • —Tags are mutable pointers, not versions. Pinning image digests is safer for Vercel-style build pipelines and reproducible deploys.
  • —Platform mismatches come from manifest metadata. Multi-arch images need explicit checks before shipping ARM/local builds to x86 servers.

  Source: news.hada.io/topic?id=30004Read original →
• #0002

  #0002Infra & SaaSGeekNews5 hours ago

  Building Durable Workflows on `Postgres`

  50radar

  Checkpointing state in the database lets jobs resume after crashes. It cuts orchestration overhead when a small product already runs on Postgres, but complex branching still needs care.

  • —Durable workflows persist completed steps as checkpoints, so a crash restarts from the last finished step instead of rerunning everything.
  • —External orchestrators like Temporal, Airflow, and AWS Step Functions add a central coordinator plus storage; that raises operational weight.
  • —A Postgres-based design fits small SaaS backends already using the DB, especially for billing, emails, imports, and LLM batch jobs.

  Source: news.hada.io/topic?id=29999Read original →
• #0003

  #0003Infra & SaaSvercel_blog18 hours ago

  `Vercel` switches function invocations to per-unit billing

  100radar

  VercelFrontend cloud platform — optimized for Next.js deployment

  Function usage now maps directly to actual calls. The rate is unchanged, but billing becomes smoother for small teams and bursty apps.

  • —Pro customers pay $0.0000006 per invocation, equivalent to the previous $0.60 per 1M invocations package rate.
  • —The change starts from the next billing cycle; current effective rates stay unchanged until the existing cycle ends.
  • —Per-unit billing reduces the chance that Vercel Functions usage eats a large chunk of monthly included credits at once.
  • —Applies to Pro and new Enterprise customers, so active Vercel apps should recheck cost dashboards after renewal.

  Source: vercel.com/changelog/function-invocations-now-billed-perRead original →