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.

referencesprovidersgeneric.md

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

Data Storage — Generic (self-hosted / open-source)

The default answer when no cloud is named. These are the engines the SKILL.md options map to, self-hosted or run anywhere.

Engine mapping → options

  • Relational/SQL → PostgreSQL (rich types, JSONB, materialized views, strong default) or MySQL/MariaDB (huge ecosystem, simple replication).
  • Document → MongoDB (flexible schema, secondary indexes, multi-doc transactions in recent versions).
  • Key-value → Redis (in-memory, rich structures; also a cache — see caching) or Riak (durable, distributed).
  • Wide-column → Cassandra (leaderless, write-heavy, tunable consistency) or HBase (Hadoop ecosystem).
  • Graph → Neo4j.
  • Connection pooler → PgBouncer (Postgres), ProxySQL (MySQL).

Limits / things that bite (verify against current docs)

  • A single relational node's practical ceiling is roughly ~1k QPS and low-TB datasets before replicas/sharding (→ back-of-the-envelope); exact numbers depend on schema, indexes, and query mix.
  • Postgres connections are processes — the default max_connections is low (often ~100); exceed it and new connections error. Pool with PgBouncer.
  • MySQL async replication can lag and lose the un-replicated tail on failover; enable semi-sync if you can't afford that loss.
  • Cassandra: consistency is tunable per query (ONE/QUORUM/ALL) — picking ONE for both read and write gives no read-your-writes guarantee.

Trade-offs specific to self-hosting

  • You own failover, backups, replica promotion, and resharding — no managed automation. Cheaper and portable (no lock-in), but operationally heavy.
  • Sharding is mostly manual (app-level routing or a layer like Vitess/Citus); managed clouds hide more of this.

Pitfalls

  • Defaulting to NoSQL for "scale" when one Postgres node would serve the load.
  • Running without a connection pooler and hitting max_connections under spike.
  • Treating self-managed async replicas as strongly consistent.
  • No tested failover/restore runbook — replication is not a backup.

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