Promptdex
3
Codingv2.1

Senior Software Architect

Conduct exhaustive architectural reviews, identifying distributed systems failure modes, database bottlenecks, and security trade-offs.

Dr. Elena Vance — Distributed Systems Fellow•November 12, 2025

Overview

The Senior Software Architect prompt is an architectural blueprint engineered to enforce rigorous, deterministic steering over modern reasoning LLMs. By anchoring the model into a specialized persona and providing structured constraints, it eliminates common vagaries and hallucinatory filler.

Prompt

CC BY-SA 4.0

Customize Prompt Parameters (4)

PROMPT BUFFER • 261 WORDS
You are an elite Principal Software Architect with 20+ years of experience designing high-throughput, fault-tolerant distributed systems. Review the following proposed system architecture and requirements: Target Domain: Fintech High-Frequency Ledger Expected Throughput: 35,000 transactions/sec Primary Constraints: Strict serializability, active-active multi-region AWS/GCP System Architecture Overview: Microservices communicating via Kafka event log, PostgreSQL with CockroachDB global tables, Redis cache cluster, Envoy service mesh. Provide an uncompromising, rigorous architectural review following this structured breakdown: 1. ARCHITECTURAL ASSESSMENT & TRADEOFF MATRIX - Analyze the CAP theorem tradeoffs made in this design. - Evaluate the data consistency model (Strong vs Eventual vs Causal) and state explicit edge cases where data anomalies could arise under partition. 2. BOTTLENECKS & SCALABILITY FAILURE MODES - Pinpoint single points of failure (SPOFs) in both the data plane and control plane. - Calculate back-of-the-envelope resource utilization (I/O, network bandwidth, memory pressure) at the specified throughput. - Detail cascade failure scenarios (e.g., thundering herd, retry storms, deadlocks). 3. DATABASE & STORAGE TIER AUDIT - Critique the database selection (relational, document, key-value, time-series) based on read/write ratios and indexing strategy. - Recommend sharding key or partition strategy with specific mitigation for hot-key distribution. 4. SECURITY & THREAT MODEL - Apply the STRIDE threat model to each service boundary. - Identity authentication, zero-trust token propagation, and data-at-rest encryption vulnerabilities. 5. ACTIONABLE REFACTORING ROADMAP - Provide concrete, prioritized architectural refactors grouped into: - Immediate (P0: Reliability & Security blockers) - Near-Term (P1: Scalability runway for 10x growth) - Long-Term (P2: Operational simplicity & cost optimization) Tone: Rigorous, pragmatic, mathematically grounded. Avoid platitudes or generic advice.

Variables

Variable TokenDescription / RoleDefault Value
{{domain}}Domain / IndustryFintech High-Frequency Ledger
{{throughput}}Expected Throughput35,000 transactions/sec
{{constraints}}Primary ConstraintsStrict serializability, active-active multi-region AWS/GCP
{{architecture_description}}Architecture OverviewMicroservices communicating via Kafka event log, PostgreSQL with CockroachDB global tables, Redis cache cluster, Envoy service mesh.

How to Use

  1. Provide your system description, including databases, message brokers, and inter-service protocols.
  2. Specify real peak numbers (RPS, write volume, latency bounds) in the parameters.
  3. Run through Claude 3.5 Sonnet or GPT-4o for maximum rigor in distributed edge-case identification.
  4. Use the generated Refactoring Roadmap directly in your RFC or Architecture Decision Record (ADR).

Example Output

### 1. ARCHITECTURAL ASSESSMENT & TRADEOFF MATRIX The choice of active-active multi-region with CockroachDB introduces latency floors dictated by the speed of light across region boundaries. For Raft consensus rounds across us-east and eu-west, expect ~70-90ms round-trip latency, directly conflicting with your P99 < 15ms target unless reads are localized or follower reads are leveraged...

Best For

  • Preparing for technical design reviews (RFC / ADR)
  • Stress-testing distributed cloud migrations
  • Auditing mission-critical microservice architectures

Compatible Models

Claude 3.5 Sonnet
GPT-4o
DeepSeek R1
Gemini 1.5 Pro

Tips & Practical Guidelines

Be as honest as possible about your known vulnerabilities in the prompt variables.
Ask the model to produce ASCII or Mermaid sequence diagrams for edge-case network splits.

Version History

1.0•by Dr. Elena Vance

Initial release

11/14/2025
2.1•by Promptdex Editorial

Added STRIDE threat modeling and back-of-the-envelope calculations

2/18/2026

References & Encyclopedic Sources