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

/data-storage

@228d57d
Run it yourself

This skill should be used when the user asks "SQL or NoSQL", "which database", how to design a "data model" or "schema design", picks an "indexing" strategy, needs "sharding" or "partitioning", sets up "replication" (leader-follower / multi-leader), defines a "primary key"/"sort key", asks whether to "denormalize", or weighs "polyglot persistence". Use it whenever a design must decide where records live, how they are keyed and accessed, and how the store scales past one node — even if the user just says "store the data".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/data-storage

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

referencesprovidersazure.md

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

Data Storage — Azure

Service mapping → options

  • Azure SQL Database — managed relational (SQL Server engine); auto-backups, read replicas, geo-replication, elastic pools. The default managed SQL. Azure Database for PostgreSQL/MySQL when you need those engines.
  • Cosmos DB — globally distributed multi-model: key-value, document (Mongo API), wide-column (Cassandra API), graph (Gremlin). Maps to all the NoSQL options; auto-sharded by a partition key, single-digit-ms reads.
  • Azure Cache for Redis — managed Redis (see caching), not a system of record.

Limits / things that bite (verify against current docs)

  • Cosmos DB: throughput is provisioned in RUs (request units); a single logical partition has a size cap (~20 GB) and a per-partition RU ceiling, so a bad partition key creates hot partitions that throttle. Choose a high-cardinality, evenly-accessed partition key — it can't be changed later without a data migration.
  • Cosmos offers five consistency levels (strong → eventual); stronger levels cost more RUs and add cross-region latency. This is a knob the generic model doesn't have — pick deliberately (consistency theory → consistency-coordination).
  • Azure SQL has DTU/vCore service tiers that cap CPU/IO/connections; hitting the tier ceiling throttles. Connection limits scale with tier.

Provider-specific trade-offs

  • Cosmos DB's turnkey multi-region writes are powerful but expensive and Azure-specific (lock-in); the multi-region consistency choice is yours to own.
  • Azure SQL hides patching/HA but the API-compatibility layer (e.g. Mongo/Cassandra on Cosmos) is not 100% — verify the features you depend on.

Pitfalls

  • Under-provisioning RUs → throttling (429s) under load; or over-provisioning → large bills.
  • Choosing a low-cardinality Cosmos partition key and hitting the 20 GB / hot- partition wall.
  • Defaulting Cosmos to strong consistency everywhere and paying latency/RU cost where eventual would do.

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 data-storage skill is an architectural decision-making guide for selecting and designing database systems. It is entirely documentation-based and contains no executable code, network operations, or security risks.

  • 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/data-storage