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

/messaging-streaming

@228d57d
Run it yourself

This skill should be used when the user designs a "message queue", reaches for "Kafka", "RabbitMQ", "SQS", "Kinesis", "pub/sub", or "event-driven" architecture, asks about "async processing", "background jobs", "stream processing", or wrestles with "exactly-once vs at-least-once", "delivery guarantees", "message ordering", "duplicate handling / dedup", "dead letter queue", "backpressure", "saga orchestration", or "durable workflow". Use it whenever a slow or spiky operation should move off the request path, or two services must be decoupled, even if the user doesn't say "queue".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

referencesprovidersazure.md

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

Messaging & streaming — Azure

Service mapping → the generic options

  • Service Bus (Queues) — managed work queue; at-least-once, sessions for per-key ordering, built-in dead-lettering, scheduled/deferred messages, duplicate detection within a window. The default enterprise queue.
  • Service Bus (Topics/Subscriptions) — pub/sub fan-out with per-subscription filters. Use when multiple consumers need filtered copies of events.
  • Event Grid — lightweight event routing/pub-sub for reactive, event-driven integration (resource events, custom topics). Push-based, at-least-once.
  • Event Hubs — partitioned, replayable log (the Kafka/Kinesis analog); ordering per partition, consumers track offsets; exposes a Kafka-compatible endpoint. Use for high-throughput streaming/telemetry and replay.

Decision-changing limits (verify against current docs)

  • Service Bus message size depends on tier (Standard ~256 KB; Premium larger); big payloads → blob + claim-check.
  • Sessions are how you get FIFO/per-key ordering on Service Bus — without a session the queue is competing-consumer (no order). One session = one consumer.
  • Service Bus duplicate detection works within a configured time window only; beyond it, consumers must still be idempotent.
  • Event Hubs throughput is bought in throughput units / processing units; parallelism = partition count, fixed at creation (plan ahead). Ordering per partition only; a hot partition key throttles one partition.

Provider-specific trade-offs

  • Service Bus (queues/topics) vs. Event Hubs/Event Grid is the queue-vs-stream-vs- event-routing split: Service Bus for command/job processing with rich delivery semantics; Event Hubs for high-volume replayable streams; Event Grid for reactive routing.
  • Premium tier buys predictable performance and larger messages at higher cost.
  • For durable workflows Azure offers Durable Functions (orchestration as code on Functions) — compare with Temporal in temporal.md.

Pitfalls

  • Expecting FIFO from a plain Service Bus queue — you must use sessions.
  • Treating duplicate detection as exactly-once beyond its window → double effects.
  • Fixing Event Hubs partition count too low and discovering it can't be raised without recreating — over-provision early.
  • Ignoring the dead-letter sub-queue Service Bus auto-populates (max-delivery, expiry, filter failures) — monitor and drain it.

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 skill provides architectural guidance and reference material for messaging and streaming systems. It contains no executable scripts, network operations, or security risks. All content is strictly educational and design-oriented.

  • 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/messaging-streaming