Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/blob-store

@228d57d
Run it yourself

This skill should be used when the user wants a "blob store" or "object storage", names "S3" or an S3-compatible store, needs to "store images / video / files", asks about "multipart upload" or "resumable upload", "signed / presigned URLs", "media storage", "unstructured data at scale", object "versioning", storage "tiering" (hot/cold/archive), or "erasure coding" vs replication for durability. Use it whenever a design must hold large unstructured objects (photos, video, backups, logs, ML datasets) and serve them cheaply and durably, even if the user just says "where do we put the files".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/blob-store

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersazure.md

≈658 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Blob store — Azure

Service mapping

  • Azure Blob Storage — the object store, inside a storage account → containers → blobs. Block blobs are the object-storage workhorse (uploaded as blocks then committed — Azure's multipart); append blobs suit log appends; page blobs back disks (not general object storage).
  • Access tiers (the tiering knob) — Hot, Cool, Cold, and Archive (offline; rehydrate to an online tier over hours before reading). Set per-blob or as an account default.
  • Redundancy (the durability knob, set on the account) — LRS (replicas in one datacenter), ZRS (across availability zones), GRS/GZRS (asynchronous copy to a second region), RA-GRS (read access to the secondary). Pick by failure domain you must survive.
  • Azure CDN / Front Door — CDN in front of the blob origin (→ content-delivery).
  • SAS (Shared Access Signature) — Azure's signed-URL equivalent: scoped, time-limited, per-blob or per-container grants.

When to pick which

Hot for actively served blobs; Cool/Cold for backups and infrequently read data (cheaper storage, higher access cost, minimum retention periods); Archive for compliance retention off the request path. LRS for cheapest single-region; ZRS for AZ resilience; GRS/GZRS for region loss.

Limits / things that bite (verify against current docs)

  • Block-blob max size is a function of max block size × max block count; large blobs require the block (multipart) path.
  • Archive is offline — you must rehydrate (hours) to Hot/Cool before a read; plan it as async.
  • Cool/Cold/Archive have minimum storage-duration charges and per-GB retrieval costs; churny or tiny blobs can cost more in a cool tier.
  • Redundancy is largely an account-level setting — mixing requirements may mean multiple accounts.
  • GRS replication to the secondary region is asynchronous → possible data loss window on failover.

Provider-specific trade-offs

  • Tight integration with Entra ID, Event Grid (blob events), and lifecycle management policies; convenient but Azure-specific.
  • Account-scoped redundancy/throughput limits make the storage-account boundary a real design unit, unlike S3's flatter bucket model.

Pitfalls

  • Reading from Archive without budgeting rehydration latency → timeouts.
  • No lifecycle policy to delete old versions/snapshots or tier down cold data → silent growth.
  • Over-broad or long-lived SAS tokens (especially account-level SAS) — scope to blob + short expiry.
  • Serving hot blobs from origin without Front Door/CDN → egress and throughput pressure.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The blob-store skill is a comprehensive educational resource and architectural guide for designing object storage systems. It contains technical documentation, trade-off analyses, and provider-specific configurations for major cloud platforms. No malicious patterns, executable code, or security risks were identified.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/blob-store