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

/sequencer

@228d57d
Run it yourself

This skill should be used when the user needs a "unique ID generator", "distributed IDs", a "Snowflake ID", asks "UUID vs auto-increment", wants a "time-sortable ID", a "monotonic sequence", a "ticket server", or "ID generation at scale". It gives a menu of ID schemes (UUID/ULID, Snowflake-style, DB ticket/range) with their causality, ordering, and clock-skew trade-offs. Use it whenever a design needs collision-free identifiers across many nodes, even if the user doesn't say "sequencer".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

referencesprovidersaws.md

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

Sequencer — AWS

Service mapping

There is no dedicated AWS ID-generation service — the generic recipe (a Snowflake library, ULID/UUIDv7, or a ticket row) is the answer. What AWS changes is where you store and shard the ID and how you run the allocator:

  • DynamoDB — IDs are your partition key. A monotonic/sequential key concentrates writes on one partition (hot partition); use a high-cardinality key (UUIDv7/ULID/Snowflake) or add a write-sharding prefix. DynamoDB has no auto-increment; an atomic-counter item (UpdateItem ADD) can act as a small ticket server but serializes on that one item.
  • Aurora / RDS (MySQL, Postgres) — native AUTO_INCREMENT/SEQUENCE and the ticket-server pattern work as in generic. Aurora's single writer means a single sequence still serializes through it.
  • Lambda / ECS / EC2 — host the Snowflake/ULID library here. For Snowflake, the challenge is node-ID assignment under autoscaling (see below).
  • ElastiCache (Redis) — INCR/INCRBY gives an atomic counter or a fast range allocator (claim a block with INCRBY), backed by Redis durability settings.

Limits / things that bite (verify against current docs)

  • DynamoDB partition throughput is capped per partition (order of a few thousand WCU); a sequential partition key funnels all new writes there. This is the most common ID-related AWS failure — partitioning fix lives in data-storage.
  • Lambda has no stable node identity — concurrent executions scale elastically and reuse nothing, so a static Snowflake node id is unsafe. Lease a node id (e.g. from a DynamoDB item with a TTL) or prefer ULID/UUIDv7 which need no node id.
  • Clock: EC2/Lambda clocks are NTP-synced but can still step; keep the rewind guard. (Verify current quotas against AWS docs — they drift.)

Provider-specific trade-offs

  • Choosing DynamoDB strongly nudges you toward UUIDv7/ULID/Snowflake (high cardinality) and away from sequential keys — a real design constraint, not a preference.
  • An atomic-counter item or Redis INCR ties your ID rate to one item/key's throughput; range-allocate to relieve it.

Pitfalls

  • Sequential ID as a DynamoDB partition key → hot partition and throttling.
  • Static Snowflake node ids on Lambda/Fargate → duplicates under scale-out.
  • Assuming DynamoDB can auto-increment — it can't; you build the allocator.

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

    This skill provides architectural guidance and design patterns for implementing distributed unique ID generators. It contains no executable code or malicious instructions.

  • 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/sequencer