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.

referencesprovidersaws.md

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

Data Storage — AWS

Service mapping → options

  • RDS (Postgres/MySQL/MariaDB) — managed relational; automated backups, read replicas, Multi-AZ failover. The default managed SQL.
  • Aurora — RDS-compatible (Postgres/MySQL) with a distributed storage layer: up to 15 low-lag read replicas, fast failover, storage auto-grows. Pick over plain RDS when you need more read scale and quicker failover.
  • DynamoDB — managed key-value + document; partition key (+ optional sort key), single-digit-ms reads, on-demand or provisioned capacity, auto-sharded. Maps to key-value / wide-column options.
  • ElastiCache — managed Redis/Memcached (see caching), not a system of record.
  • Keyspaces (managed Cassandra), Neptune (graph), DocumentDB (Mongo-compatible) — use when you specifically need those models.

Limits / things that bite (verify against current docs)

  • DynamoDB: item size capped (~400 KB); a single partition has a throughput ceiling, so a hot partition key throttles even when total capacity is spare — design the PK for even spread. Strongly-consistent reads cost more RCUs and only work on the base table, not global secondary indexes (GSIs are eventually consistent).
  • RDS/Aurora: Multi-AZ failover takes seconds to ~a minute; an async read replica can lag and lose the tail if promoted. Connection limits scale with instance size — front with RDS Proxy to survive Lambda/spiky fan-out.
  • Cross-AZ data transfer is billable.

Provider-specific trade-offs

  • DynamoDB is serverless and scales effortlessly but locks you into its data model and query style (no joins, access patterns must be designed up front); migrating off is real work.
  • Aurora decouples compute from storage (cheap replicas) but is AWS-only.
  • On-demand DynamoDB is convenient but pricier than well-sized provisioned capacity at steady high load.

Pitfalls

  • Choosing DynamoDB then fighting it with scan-heavy/ad-hoc queries it isn't built for — that's a relational workload.
  • Hot partition key throttling while the table looks under-provisioned.
  • Skipping RDS Proxy and exhausting connections under serverless fan-out.
  • Assuming GSIs are strongly consistent.

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