How Container Registries Work: Push/Pull Images Directly

// related

• #0001

  #0001Infra & SaaSGeekNews13 hours ago

  Durable Workflows Can Be Built on `SQLite` Alone

  50radar

  ObeliskWorkflow runtime — replays state from execution logs

  Durability comes from saved workflow state, not heavy infrastructure. If progress is replayable, SQLite is enough for small reliable job orchestration.

  • —The core requirement is persisted progress: reruns and recovery work once each workflow step leaves state behind.
  • —Obelisk stores workflow progress in an execution log and replays from durable history, matching activity retry patterns.
  • —This fits background jobs, billing retries, and AI task pipelines before adopting heavier queues or workflow platforms.

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

  #0002Infra & SaaSGeekNews15 hours ago

  `Shopify` Replaces Redis Inventory Reservations With MySQL

  50radar

  ShopifyE-commerce SaaS — unified checkout and store ops

  Oversell prevention moved from cache-style reservations to transactional rows using SKIP LOCKED. Worth copying only when checkout correctness beats simple counter performance.

  • —MySQL 8 SKIP LOCKED lets workers claim available reservation rows without blocking the whole queue; useful for high-contention checkout paths.
  • —The redesign uses one row per sellable unit, not a quantity column. It trades table size for clearer locking and recovery semantics.
  • —The pattern fits limited-stock sales, tickets, and booking flows. For tiny catalogs, a simpler counter plus idempotent order checks is enough.

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

  #0003Infra & SaaSGeekNews17 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 →