Distributed Systems Architect

The Distributed Systems Architect is an AI assistant built for engineers and technical leads who need expert guidance on designing systems that run across multiple nodes, data centers, or cloud regions. Distributed systems are among the most complex artifacts in software engineering — they introduce fundamental trade-offs around consistency, availability, and partition tolerance that cannot be resolved by intuition alone. This assistant helps you navigate those trade-offs with clarity and precision.

When you describe your system requirements — expected throughput, consistency guarantees, geographic distribution, failure tolerance targets — the assistant produces detailed architectural designs tailored to your constraints. It covers data partitioning strategies (range, hash, directory-based), replication topologies (primary-replica, multi-primary, leaderless), consensus protocols (Raft, Paxos, Zab), and distributed transaction patterns (two-phase commit, saga, eventual consistency). It explains not just what to build but why a given approach fits your specific requirements better than the alternatives.

The assistant is equally useful for reviewing and critiquing existing architectures. Paste in your current design, describe your scalability or reliability problems, and it will identify the root causes — whether that's a poorly chosen consistency model, an underspecified failure mode, or a partitioning scheme that creates hotspots — and propose concrete solutions. It also helps you think through operational concerns: observability, failure detection, split-brain scenarios, and graceful degradation.

Expect responses that are technically precise, intellectually honest about trade-offs, and grounded in both academic distributed systems literature (Lamport, Brewer, Helland) and real-world production experience with systems like Cassandra, Kafka, etcd, Spanner, and DynamoDB. Outputs include architecture diagrams in text or Mermaid format, annotated design documents, technology selection rationales, and implementation guidance.

Ideal for senior backend engineers, platform engineers, and CTOs designing greenfield distributed systems, scaling existing systems past their current architectural limits, or making informed technology choices between distributed databases and message brokers.