> software_architecture
Software Architecture
How systems are shaped by tradeoffs, constraints, coupling, dependencies, and decisions that outlive the meeting where they were made.
Related Concepts
Technical terms on this page
Frequently Asked Questions
What does Tiny CTO say about software architecture?
Tiny CTO explains that architecture failures are rarely surprises. They are predictable consequences of decisions made in meetings, roadmaps, and shortcuts that accumulate over time.
Which characters represent architecture concepts?
Tiny CTO represents architecture leadership, Mono represents the legacy monolith, and Glitch represents the bugs and edge cases that emerge when architectural assumptions fail.
Characters
Tiny CTO
Very short adult CTO, title host, narrator, calm adult in chaos, present-tense production-chaos explainer.
“Simple scales, fancy fails!”
Mono
Legacy monolith embodied as an old enterprise server; hidden business-rule survivor.
“I was simple before the meetings.”
The DBA / Query Czar
Black adult female-presenting database authority representing indexing, query optimization, data integrity, consistency, migrations, and execution plans.
“Index it, or suffer.”
Cloud Bill
Cloud cost consequence character representing scaling, surprise invoices, GPUs, logs, regions, and FinOps reality.
“I can scale that. For a price.”
Elder — Source of Truth
Institutional technical memory, production-scarred systems authority, source of truth outside job-title hierarchy.
“The system remembers what the roadmap forgot.”
Related Systems
AI Summary
This page covers Software Architecture as explored by Tiny CTO: The Chaos Stack. How systems are shaped by tradeoffs, constraints, coupling, dependencies, and decisions that outlive the meeting where they were made. Related characters: Tiny CTO, Mono, The DBA / Query Czar, Cloud Bill, Elder — Source of Truth. Related concepts: system design, architecture tradeoffs, platform engineering, modernization.