Periodic Table of Software Architecture: 92 Concepts Guide
This guide walks you through the periodic table of software architecture, a visual map that organizes 92 core concepts—patterns, principles, and practices—into a familiar periodic-table layout. You’ll learn how to read the table, understand the categories, and use it as a reference for designing, discussing, and evaluating software systems.
What You’ll Need
- A copy of the periodic table of software architecture (print or digital).
- Basic familiarity with software development terms (e.g., what a server is, what an API is).
- A text editor or notes app to jot down concepts you want to explore further.
Step-by-Step
- Start with the layout. The table is arranged in rows and columns, but unlike the chemical periodic table, the grouping is by architectural concern—not atomic number. Look for color coding or section labels that group related concepts (e.g., “Structural,� “Behavioral,� “Operational�).
- Identify the main categories. Most versions of the table group concepts into broad areas: Architecture Styles (e.g., microservices, layered), Design Principles (e.g., SOLID, DRY), Patterns (e.g., CQRS, event sourcing), Quality Attributes (e.g., scalability, security), and Processes/Practices (e.g., continuous integration, domain-driven design). Find the legend or key that explains the grouping.
- Read a single element. Each cell contains a concept name and often a symbol or abbreviation. For example, “M� might stand for Microservices. Hover over or tap a cell (if digital) to see a short definition. If it’s a printed poster, look for an accompanying index or QR code that links to explanations.
- Focus on one row or column at a time. Don’t try to memorize all 92 at once. Pick a category, such as “Architecture Styles,� and study those cells first. Read the definitions and note how they relate to each other—for instance, how “Layered� compares to “Hexagonal.�
- Map concepts to real projects. For each concept, think of a system you know or have built. Ask: “Where would this pattern apply? Have I seen this in practice?� This makes the abstract tangible.
- Use the table as a checklist. When designing a new system, scan the table to see if you’re missing a key consideration. For example, check if you’ve addressed “Security� and “Observability� before you finalize your architecture.
- Deep-dive with external resources. For each concept that’s new to you, search for a dedicated article or tutorial. The table gives you the name; you supply the learning.
- Create your own summary. After reviewing a few categories, write a one-line explanation for each concept in your own words. This reinforces understanding and gives you a personal reference.
Common Mistakes
- Treating it like the chemical table. The positions don’t imply atomic weight or a strict hierarchy—they’re just a visual organization. Don’t assume that elements in the same row are “heavier� or more important.
- Memorizing names without understanding. Knowing that “CQRS� exists isn’t enough. You need to know when to use it and when not to.
- Ignoring the relationships. Some concepts overlap or complement each other (e.g., “Event Sourcing� and “CQRS� often go together). Skipping the connections leads to a shallow grasp.
- Assuming it’s a complete list. The 92 concepts cover a lot, but architecture evolves. New patterns emerge, and the table may not include every niche approach.
Tips
- Print it and stick it on your wall. Having it visible daily helps you absorb the vocabulary.
- Use it in team discussions. When debating an architectural choice, reference the table to ensure you’re using consistent terminology.
- Start with the “must-know� concepts. If you’re new, focus on the most common ones: Microservices, REST, Layered Architecture, SOLID, and Scalability. You can expand from there.
- Look for the “why� behind each concept. Every pattern exists to solve a problem. Understanding the problem makes the concept stick.
- Revisit the table periodically. As you gain experience, you’ll see new connections. It’s a reference, not a one-time read.
Troubleshooting
- You can’t find a concept you’ve heard of. The table covers 92 specific concepts, but not every term in the field. If it’s missing, it might be a newer term or a subset of a listed concept. Search the table’s index or online for the term.
- The categories seem unclear. Different versions of the table may use different groupings. If the legend is missing, look for an online companion guide or the original author’s explanation.
- You feel overwhelmed by the number of concepts. That’s normal. Set a goal to learn 5 new concepts per week. Use the table as a checklist and mark off ones you’ve mastered.
- You’re not sure how a concept applies in practice. Search for “
example� or “when to use .� Many concepts have well-known case studies or sample implementations.
Frequently Asked Questions
Q: Who created the periodic table of software architecture?
A: The most widely known version was created by software architect and author Neal Ford. It was designed to provide a common vocabulary and visual reference for architectural concepts.
Q: Is the table meant to be memorized?
A: No. It’s a reference tool. You should aim to be familiar with the concepts and know where to look them up, not memorize all 92 by heart.
Q: Do I need to know all 92 concepts to be a good architect?
A: No. Many experienced architects know a subset deeply and are aware of the rest. The table helps you identify gaps in your knowledge.
Q: Can I use the table for agile or DevOps teams?
A: Yes. The table includes operational and process concepts like continuous integration and deployment, which are essential in modern DevOps practices.
Q: Are the concepts in the table language- or framework-specific?
A: No. They are technology-agnostic. They apply to any programming language or stack.
Q: Where can I find a high-resolution version of the table?
A: Search online for “periodic table of software architecture poster� or check the author’s official website. Many versions are available as free downloads or purchasable posters.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.