software-engineering-eng-distributed

What problem does it solve?

It helps you reason rigorously about distributed system trade-offs—so you can design architectures that behave correctly under partitions, failures, and retries.

Core Features & Use Cases

• Consistency, CAP, and failure-mode analysis: Identify per-entity consistency requirements and predict behavior under network partitions and common failure modes.
• Replication and partitioning strategy: Choose replication topology (single-leader, multi-leader, leaderless) and partition keys (range, hash, rebalancing) to match your scale and correctness needs.
• Operational design for correctness: Apply idempotency, delivery semantics, stream-processing considerations, and distributed design patterns like event sourcing, CQRS, and sagas.

Use case example: You’re reviewing a Kafka-based payments/order pipeline and need to determine the correct delivery semantics, ordering guarantees, idempotency approach, and the consistency model for each data entity—then produce concrete recommendations and failure-mode mitigations.

Quick Start

Ask the skill to analyze a distributed system you describe and to return a failure-mode catalog, a consistency/partitioning strategy, and top corrective recommendations.