solution-architecture

Guide solution architecture decisions on trade-offs, technology selection, and production failure modes.

3|Updated Apr 14, 2026

Search Tags:#microservices #trade-offs #solution architecture #technology selection #non-obvious failure modes

Ready to run

npx skills add https://github.com/MayaDispeler/TheOrqestra --skill solution-architecture-mayadispeler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: solution-architecture
Source: https://github.com/MayaDispeler/TheOrqestra/tree/main/skills/solution-architecture
Command: npx skills add https://github.com/MayaDispeler/TheOrqestra --skill solution-architecture-mayadispeler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill serves as an expert reference for solution architecture, addressing trade-offs, technology selection, and non-obvious production failure modes.

Core Features & Use Cases

Expert Trade-offs: Offers detailed guidelines on architectural decisions and quantifying non-functional requirements.
Technology Selection: Provides clear rules for choosing databases, async communication, service communication, and when to split monoliths.
Non-Obvious Failures: Identifies common failure modes and their fixes, such as thundering herd on cache expiry and fan-out explosion in event systems.

Quick Start

Use the solution-architecture skill to guide the architecture design for a new microservice, considering non-functional requirements and potential failure modes.

Frequently Asked Questions about solution-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I evaluate technology selection trade-offs when designing microservices?▼

Technology selection trade-offs in microservices require quantifying non-functional requirements against architectural constraints. Expert guidelines provide clear rules for choosing databases, async communication protocols, and service communication patterns based on system-specific factors.

What are common non-obvious production failure modes in microservices architecture?▼

Non-obvious production failure modes in microservices architecture include thundering herd on cache expiry and fan-out explosion in event systems. Identifying these issues early enables implementing targeted mitigation strategies before deployment.

When should I split a monolith into microservices?▼

Splitting a monolith into microservices should occur when specific architectural selection criteria are met. Expert guidelines provide clear rules determining the exact threshold for service separation based on system complexity and non-functional requirements.

How do I quantify non-functional requirements for solution architecture design?▼

Quantifying non-functional requirements for solution architecture involves evaluating detailed architectural trade-offs. This process ensures careful consideration of various structural factors and produces targeted mitigation strategies for complex system design scenarios.

What is the best way to choose between async communication and service communication patterns?▼

Choosing between async communication and service communication patterns depends on specific technology selection criteria. Expert architectural guidance provides clear rules differentiating these approaches based on system design requirements and potential failure modes.

How do I mitigate a thundering herd on cache expiry in event systems?▼

Mitigating a thundering herd on cache expiry in event systems involves implementing specific architectural fixes. Expert solution architecture guidelines identify this non-obvious failure mode and provide targeted strategies to prevent cascading production failures.