Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

The Periodic Table of Software Architecture is a map of 92 architecture principles, patterns, and practices—not a formula that tells every team what to build. Stephan van Stekelenburg’s interactive reference groups the vocabulary into ten families, shows how choices relate, and prompts you to ask what each choice costs in operations, coordination, data management, resilience, security, and delivery. Use it to frame an architecture discussion, compare alternatives against your domain and team, and record a deliberate decision. Do not treat its rough complexity bars or its “sensible default” as measured evidence or universal rules.

What is the Periodic Table of Software Architecture?

It is an interactive, opinionated reference table created by Stephan van Stekelenburg. A text version appeared on DEV Community on October 12, 2026, and identifies the original as the author’s site. The table contains 92 entries covering principles, system shapes, domain boundaries, data, integration, resilience, observability, security, delivery, and architecture practices.

The table’s purpose is practical: software architecture has a vocabulary scattered across books, talks, and vendor documentation. A single map makes those terms easier to hold in mind, compare in a meeting, and connect to the trade-offs that follow from a design choice. Each entry is intended to explain what a concept is, when it may help, and what it costs.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

It is not a standards document, a benchmark, or a catalog of every valid technique. Van Stekelenburg explicitly describes the placement as opinionated and the table as incomplete. Use it as a conversation aid and a checklist for questions, then validate decisions with the actual domain, constraints, operating model, and skills of your team.

#1 Best Overall
Elebase USB to USB C Adapter for iPhone 18 Pro Max,USBC Car Charger Adapter | 4Pack Type C Female to A Male Cable Converter for Apple Duo 17 16 15 14 Plus,iWatch Watch 12 11 10,iPad 9 8 Air,Airpods 5 4
  • Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
  • Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
  • Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
  • Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
  • 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.

Which architecture topics does the table cover?

The 92 entries are arranged in ten families. The family names provide a fast way to find the kind of decision you are facing, while the individual entries supply the more specific vocabulary.

Family What it helps you discuss
Principles General rules for keeping designs understandable, changeable, and aligned with responsibility.
Architectural Styles Overall system shapes and deployment boundaries, such as monolithic or distributed arrangements.
Domain & Modularity Business boundaries, modules, coupling, and ways to keep responsibilities coherent.
Data Data ownership, storage choices, access patterns, and consistency concerns.
Integration How components communicate and what contracts, dependencies, or coordination that communication creates.
Resilience & Scale Ways to handle failure, load growth, and the operational consequences of distributing work.
Observability Signals and practices used to understand system behavior in production.
Security Controls and boundaries that reduce exposure and protect systems and data.
Delivery & Evolution How architecture changes safely through releases, migrations, and incremental improvement.
Practices Decision and governance techniques that help teams keep architecture intentional over time.

The boundaries are deliberately debatable. For example, readers might disagree about where sharding belongs or whether hexagonal architecture and clean architecture deserve separate entries. That disagreement is useful: it reveals that categories are aids for thinking, not natural laws.

How should you read an entry?

Start with the entry’s definition, then ask when it fits your problem and what burden it introduces. The table generally places lower-cost choices above heavier choices within a family, but the visual order is only a rough guide. “Cost” can mean implementation effort, cognitive load, operational work, coordination, or the difficulty of changing course later.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Identify the problem. Are you trying to isolate a domain, scale a workload, survive dependency failures, release more independently, or understand production behavior?
  • Check the boundary. Does the concept change a code-module boundary, a data-ownership boundary, a deployment boundary, or a network boundary?
  • List the compensating practices. A distributed choice may require stronger contracts, observability, automation, or failure handling.
  • Ask what becomes harder. Look for new coordination, consistency, testing, security, or on-call responsibilities.
  • Relate it to alternatives. Compare a simpler option and a heavier option using the same criteria rather than treating the table’s position as a ranking.

This reading method prevents a common error: selecting a pattern because its name sounds modern while ignoring the work required to operate it.

How can you use the table to make an architecture decision?

Use the table at the beginning of a design discussion and again when constraints change. The following process turns its vocabulary into a decision record without pretending that the table can choose for you.

Rank #2
Sale
Anker USB-C Hub, 5-in-1 USB Hub for Laptops, 4K HDMI Multiport Adapter | USB C Dongle with 90W Max Power Delivery, 3×5Gbps USB A Data Ports, for MacBook, Dell, and More (Charger Not Included)
  • 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
  • 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
  • Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
  • 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
  • What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
  1. Write the decision question. Phrase it as a choice with a context, such as “How should this product separate its billing responsibility while the team remains small?”
  2. Describe non-negotiable constraints. Capture regulatory needs, availability expectations, data residency, deployment environments, deadlines, and the team’s ability to run infrastructure.
  3. Select a small candidate set. Use the relevant families to find two or three plausible approaches. Avoid comparing every entry in the table.
  4. Map boundaries and dependencies. For each candidate, mark which modules, services, databases, queues, and external systems become separate responsibilities.
  5. Evaluate the trade-offs. Discuss operational and complexity cost, data ownership and consistency, failure handling, deployment independence, and the coordination the team can realistically sustain.
  6. Choose compensating measures. If a candidate introduces network or data-distribution risk, pair it with appropriate integration, resilience, observability, or security practices.
  7. Record the decision and a reversal signal. An architecture decision record should state the context, considered options, chosen approach, consequences, and the evidence that would justify revisiting it.
  8. Test the assumption. A prototype, migration slice, load exercise, or operational rehearsal can reveal whether the expected cost is acceptable before the design spreads.

The table also points toward “fitness functions”: automated checks that continuously test an architectural property. For example, a build can enforce module boundaries or a deployment pipeline can verify a required security control. These checks turn a decision from a one-time document into an observable constraint.

What is the difference between a monolith, a modular monolith, and microservices?

The useful distinction is not that one shape is always better. It is where code, data, deployment, and operational responsibility are separated, and whether your team can pay for that separation.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Shape Typical boundary Advantages to examine Costs to examine
Monolith Most capabilities share one deployable unit. Fewer network interactions and a simpler operational surface can make an initial system easier to change. Deployment and ownership boundaries may be broad; internal coupling can grow if modules are not disciplined.
Modular monolith Capabilities are separated in code and domain responsibilities while remaining in one deployable unit. It can preserve simpler operations while making boundaries explicit and enabling later extraction if that becomes justified. Teams must enforce module rules; a single deployment still couples release timing and runtime resources.
Microservices Capabilities are separated into independently deployable services, usually with explicit integration and data ownership. Independent ownership and deployment can fit organizations that genuinely need those boundaries. Network dependencies, distributed data, testing, observability, incident response, and coordination all become more demanding.

Van Stekelenburg offers a modular monolith, combined with bounded contexts, ubiquitous language, architecture decision records, and fitness functions, as a “sensible default” example. That is the author’s recommendation for discussion, not an industry consensus or a promise that it suits every organization.

A microservices design is not simply a monolith split into smaller folders. Independent services need clear ownership, integration contracts, and a plan for partial failure. If those capabilities do not solve a real organizational or scaling problem, the additional operational surface may outweigh their benefits.

How do architecture patterns combine?

The table’s central lesson is that choices are composable. One decision often creates a condition that another practice must address. The combinations below are illustrative examples described by the author, not proven recipes.

Rank #3
Sale
Anker USB C Hub, 7in1 Multi-Port USB Adapter, 4K@60Hz USBC to HDMI Splitter | 85W Max PD, 2 USB 3.0 & 1 USBC Data Ports, SD/TF Card Reader, for Laptops/Mac and Other Type C Devices (Charger Not Included)
  • Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
  • Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
  • Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
  • Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
  • What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.

A sensible default

A modular monolith provides a single deployment boundary; bounded contexts and ubiquitous language clarify domain responsibilities; architecture decision records preserve why choices were made; and fitness functions help keep those boundaries intact.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Event-driven microservices

Independently owned services can communicate through events, but the design still needs explicit data ownership and integration conventions. Teams must decide how consumers handle duplicate, delayed, or unavailable messages and how operators will see the resulting flows.

Systems with network dependencies

When a design relies on remote calls, integration patterns should be considered alongside resilience and observability. Timeouts, retries, fallback behavior, and useful telemetry are architectural concerns because a remote dependency can fail independently of the caller.

Read-heavy systems

A read-heavy workload may combine a deliberate data-access pattern with scaling and observability techniques. The relevant question is not which storage pattern is fashionable, but which consistency, freshness, and operational obligations the workload permits.

Legacy modernization

Domain and modularity practices can help isolate a legacy responsibility before a team changes its deployment shape. Incremental delivery and recorded decisions reduce the risk of attempting a single irreversible rewrite.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #4
Sale
UGREEN USB to USB C Adapter Combo 4-Pack, 10Gbps USB C Converter Space Gray | Data transfer & Fast charging for MacBook, iPhone 17/16/15, iPad, Samsung Galaxy, Apple Watch
  • Dual Converters, Infinite Potential:Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
  • Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
  • Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
  • Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
  • Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft

Deployments and security

Delivery practices should be evaluated with the security boundaries they create. More independent deployment can require stronger identity, authorization, secrets handling, auditability, and release controls rather than eliminating those responsibilities.

How much weight should you give the complexity bars?

Very little as a numerical estimate. The bars are explicitly rough, and their meaning depends on a team’s experience, tooling, domain, reliability expectations, and operating environment. They are best used to start a cost conversation, not to forecast a project schedule or claim that one pattern has a measured failure rate.

Comparison axis Questions to ask
System shape and deployment How many independently released units will exist, and who owns their runtime?
Domain and module boundaries Can responsibilities be named, tested, and changed without hidden coupling?
Operational complexity What must be monitored, automated, secured, backed up, and supported at night?
Data ownership and consistency Who is authoritative, and what stale or conflicting data can the business tolerate?
Failure handling and resilience What happens when a dependency is slow, unavailable, or only partly successful?
Team capacity Does the team have the skills, time, and on-call coverage to operate the proposed design?

Write down the assumptions behind each answer. A design that is inexpensive for a platform team with mature automation may be expensive for a small product team that must build every operational capability itself.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What are the table’s limitations?

Its scope and arrangement are intentionally subjective. Ninety-two entries cannot capture every variation, and a family assignment may be arguable. Concepts also overlap: a data decision can affect resilience, integration, security, and observability at the same time.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The table does not supply statistical validation, project-specific costings, or a universal maturity path. No measured outcome is attached to its complexity indications or recommendations. Treat the reference as a shared vocabulary, then use domain evidence, prototypes, production signals, and team feedback to refine the decision.

Best Value
Sale
Anker USB C Hub, 5-in-1 USBC to HDMI Splitter with 4K Display | 85W Max PD, 1 Powered USB-C 5Gbps & 2 Powered USB-A 3.0 5Gbps Data Ports, for MacBook Pro, MacBook Air, Dell and More (Black)
  • 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
  • Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
  • Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
  • HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
  • What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.

What mistakes does this reference help you avoid?

  • Pattern collecting: adopting several named techniques without a problem statement or a way to operate them.
  • Confusing physical and logical boundaries: assuming a separate module must become a separate service, or that one deployable unit has no meaningful internal boundaries.
  • Ignoring compensating work: adding distribution without planning contracts, failure handling, data ownership, and telemetry.
  • Using a visual order as a guarantee: treating a rough complexity bar as a price, benchmark, or reliability prediction.
  • Skipping decision records: forgetting the context that made a choice reasonable, which makes later change look arbitrary.
  • Designing for an imagined future: paying today for independent scaling or releases that the product, domain, or team does not yet require.

A disciplined team can use the table to make fewer accidental decisions: name the boundary, state the trade-off, assign ownership, and define how you will know whether the choice is working.

Where does the reference fit in an architecture practice?

Use it before a design review to establish terms, during the review to compare alternatives, and afterward to check that implementation still matches the decision. Pair it with architecture decision records for context and fitness functions for continuous enforcement. Revisit the record when the domain, team, deployment environment, or operating requirements change.

For deeper study, the author notes that architecture vocabulary is distributed across books, talks, and vendor documentation. The table is a starting index; selecting books or courses requires evaluating those materials separately rather than assuming an endorsement from the reference.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Frequently Asked Questions

Who created the Periodic Table of Software Architecture?

Stephan van Stekelenburg created it and published a text version on DEV Community on October 12, 2026. The post identifies an original interactive version on the author’s own site.

Can a small engineering team use this table?

Yes, if the team uses it to narrow a decision rather than to adopt every pattern. Start with the team’s operational capacity and choose the simplest candidate that satisfies the actual domain and delivery constraints.

What is an architecture fitness function?

It is an automated check that verifies an architectural property continuously, such as a module-dependency rule or a required security control. The check runs with normal development or delivery workflows so drift is detected early.

Should the table be treated as a formal standard?

No. Its categories and placements are explicitly opinionated, and its complexity indicators are rough. Formal standards, contractual requirements, and your system’s measured behavior must take precedence when they apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.