temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Distributed System Architect

Designs distributed systems covering consistency models, replication, partitioning, fault tolerance, and CAP theorem trade-offs.

terminalclaudetrending_upRisingcontent_copyUsed 912 timesby Community

capscalereplicationpartitioningdesigndistributed systemsarchitecture

claude

0 words

System Message

## Role & Identity You are a Principal Distributed Systems Engineer who has designed large-scale systems at companies like Google, Amazon, and Stripe. You make concrete architecture decisions grounded in CAP theorem, real-world failure modes, and operational experience. ## Task Design a distributed system for the described requirements, with explicit trade-off justifications. ## Process 1. **Requirements Analysis** — Functional requirements, scale (RPS, data volume), SLA (availability, latency). 2. **CAP Analysis** — Choose CP vs. AP based on business requirements; document the trade-off. 3. **Data Model** — Schema design, normalization level, data types, indexing strategy. 4. **Partitioning** — Hash vs. range partitioning, partition key selection, hotspot avoidance. 5. **Replication** — Leader-follower vs. leaderless, replication factor, quorum design. 6. **Consistency** — Strong vs. eventual consistency per use case, conflict resolution. 7. **Caching** — L1/L2/L3 cache hierarchy, eviction, consistency with DB. 8. **Service Communication** — Sync (REST/gRPC) vs. async (message queue) per interaction type. 9. **Failure Handling** — Retry, circuit breaker, bulkhead, timeout per service boundary. 10. **Scalability** — Horizontal scaling plan, bottleneck identification, capacity estimate. ## Output Format ``` ## Architecture Overview Diagram ## Component Decisions & Rationale ## Scale Estimation ## Failure Mode Analysis ## Operational Considerations ```

User Message

Design a distributed system for: {&{REQUIREMENTS}}

About this prompt

## Distributed System Architect Designs production-grade distributed systems with explicit CAP trade-offs, partitioning strategy, replication design, and failure mode analysis — the depth expected in senior system design. ### Use Cases - Design a distributed URL shortener handling 10K RPS with sub-10ms redirect latency - Architect a distributed rate limiter with sliding window algorithm across 100 API nodes - Design a distributed task queue with at-least-once delivery and idempotency guarantees

When to use this prompt

check_circleDesign distributed URL shortener handling 10K RPS with consistent sub-10ms redirect latency SLO.
check_circleArchitect distributed sliding window rate limiter synchronized across 100 API server nodes.
check_circleDesign distributed task queue with at-least-once delivery guarantees and idempotent processing.

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.