Software Architect
What the architect role actually does above the code: making and recording trade-off decisions, the principles and patterns that keep a system coherent as it grows, the paradigms an architect has to reason across, security and data architecture, and the cloud and enterprise patterns a production system is actually assembled from. Twenty-six lessons that assume computer-science and system-design as a starting point and go one layer up from both — the job of choosing and defending a system's shape, not the mechanics of any one piece of it.
What Is Software Architecture, and What Does an Architect Actually DoWhat separates an architectural decision from an implementation one, and what the architect role does differently from a senior engineer.Levels of Architecture — Enterprise, Solution, and ApplicationThe three scopes architects work at, how the questions and stakeholders change at each one, and why mixing them up causes real damage.Architecture Decision Records and How to Argue a Trade-offWhat an ADR actually records, the template that makes one useful, and how to revisit a decision later without relitigating it from scratch.Communicating Architecture to Stakeholders Who Don't Read DiagramsWhy most architecture diagrams fail their audience, and how the C4 model's four levels fix that by matching detail to who's actually looking.Managing Technical Debt With Evolutionary Architecture and Fitness FunctionsTechnical debt as a deliberate trade-off, not a moral failing, and fitness functions as the automated check that keeps architecture from drifting as it evolves.Architecture Under Agile Delivery — What Actually ChangesWhere big design up front fails under iterative delivery, where some up-front design still has to survive, and how decisions actually get fed into sprints.SOLID PrinciplesThe five object-oriented design principles — SRP, OCP, LSP, ISP, DIP — with a concrete before/after code shape for each one.Domain-Driven DesignBounded contexts, ubiquitous language, and aggregates — the strategic and tactical halves of DDD, and why they decide where service boundaries go.Architectural Patterns & Dependency InjectionLayered architecture, MVC/MVP/MVVM, and hexagonal architecture, plus dependency injection as the technique that makes them work.Choosing an Architectural StyleA decision framework across monolith, microservices, SOA, serverless, and event-driven — which signals should actually drive the choice.Service-Oriented Architecture & the ESBWhat problem the enterprise service bus solved, how SOA integration differs from point-to-point and from modern event-driven integration.The Four Pillars of Object-Oriented ProgrammingEncapsulation, abstraction, inheritance, and polymorphism — what each one actually buys you, not just its definition.Functional Programming, for an ArchitectPure functions, immutability, and higher-order functions — why they matter even in a codebase that is mostly object-oriented.Reactive Programming: Streams Instead of StateModeling a system as asynchronous streams of events instead of state you poll or mutate — observables, operators, and backpressure.The Actor Model: Concurrency Without Shared MemoryHow actors, mailboxes, and message passing let concurrent code stay correct by making shared mutable state structurally impossible.Public Key InfrastructureCertificate authorities, trust chains, and revocation — the infrastructure of issuance and trust behind every certificate a system presents.The OWASP Top 10 for ArchitectsThe ten most common web application security risks, read as design decisions an architect makes up front rather than bugs a pentest finds later.Zero Trust ArchitectureWhy "never trust, always verify" replaced the perimeter model, and what actually enforces it: identity, device posture, and micro-segmentation.ETL, ELT & the Data WarehouseWhy operational databases and analytical warehouses are different systems, and how ETL and ELT move data between them.GraphQL Architecture & Schema DesignWhat a GraphQL schema actually buys an architecture over REST or gRPC, and the N+1 trap every resolver-based API eventually hits.MicrofrontendsSplitting a frontend into independently built and deployed pieces — what it buys a large team, and what it costs at runtime.Choosing a Frontend ArchitectureSPA, SSR, SSG, and hybrid rendering as an architecture decision — what actually drives the choice, not a framework tutorial.Cloud Design PatternsValet key, gatekeeper, competing consumers, and pipes and filters — cloud patterns this site's other architecture lessons don't already cover.Serverless Architecture Trade-offsCold starts, vendor lock-in, and the pay-per-execution cost model — when FaaS is the right call, and when it quietly isn't.Designing for Cost and Total Cost of OwnershipWhy the sticker price is the smallest part of a build-vs-buy decision, and how cost trades off against performance and reliability.Enterprise Architecture FrameworksWhat TOGAF's ADM cycle actually provides, and how enterprise architecture differs from solution and application architecture.
The architect role
- What Is Software Architecture, and What Does an Architect Actually DoWhat separates an architectural decision from an implementation one, and what the architect role does differently from a senior engineer.
- Levels of Architecture — Enterprise, Solution, and ApplicationThe three scopes architects work at, how the questions and stakeholders change at each one, and why mixing them up causes real damage.
- Architecture Decision Records and How to Argue a Trade-offWhat an ADR actually records, the template that makes one useful, and how to revisit a decision later without relitigating it from scratch.
- Communicating Architecture to Stakeholders Who Don't Read DiagramsWhy most architecture diagrams fail their audience, and how the C4 model's four levels fix that by matching detail to who's actually looking.
- Managing Technical Debt With Evolutionary Architecture and Fitness FunctionsTechnical debt as a deliberate trade-off, not a moral failing, and fitness functions as the automated check that keeps architecture from drifting as it evolves.
- Architecture Under Agile Delivery — What Actually ChangesWhere big design up front fails under iterative delivery, where some up-front design still has to survive, and how decisions actually get fed into sprints.
Principles & patterns
- SOLID PrinciplesThe five object-oriented design principles — SRP, OCP, LSP, ISP, DIP — with a concrete before/after code shape for each one.
- Domain-Driven DesignBounded contexts, ubiquitous language, and aggregates — the strategic and tactical halves of DDD, and why they decide where service boundaries go.
- Architectural Patterns & Dependency InjectionLayered architecture, MVC/MVP/MVVM, and hexagonal architecture, plus dependency injection as the technique that makes them work.
- Choosing an Architectural StyleA decision framework across monolith, microservices, SOA, serverless, and event-driven — which signals should actually drive the choice.
- Service-Oriented Architecture & the ESBWhat problem the enterprise service bus solved, how SOA integration differs from point-to-point and from modern event-driven integration.
Paradigms
- The Four Pillars of Object-Oriented ProgrammingEncapsulation, abstraction, inheritance, and polymorphism — what each one actually buys you, not just its definition.
- Functional Programming, for an ArchitectPure functions, immutability, and higher-order functions — why they matter even in a codebase that is mostly object-oriented.
- Reactive Programming: Streams Instead of StateModeling a system as asynchronous streams of events instead of state you poll or mutate — observables, operators, and backpressure.
- The Actor Model: Concurrency Without Shared MemoryHow actors, mailboxes, and message passing let concurrent code stay correct by making shared mutable state structurally impossible.
Security architecture
- Public Key InfrastructureCertificate authorities, trust chains, and revocation — the infrastructure of issuance and trust behind every certificate a system presents.
- The OWASP Top 10 for ArchitectsThe ten most common web application security risks, read as design decisions an architect makes up front rather than bugs a pentest finds later.
- Zero Trust ArchitectureWhy "never trust, always verify" replaced the perimeter model, and what actually enforces it: identity, device posture, and micro-segmentation.
Data & integration architecture
- ETL, ELT & the Data WarehouseWhy operational databases and analytical warehouses are different systems, and how ETL and ELT move data between them.
- GraphQL Architecture & Schema DesignWhat a GraphQL schema actually buys an architecture over REST or gRPC, and the N+1 trap every resolver-based API eventually hits.
- MicrofrontendsSplitting a frontend into independently built and deployed pieces — what it buys a large team, and what it costs at runtime.
- Choosing a Frontend ArchitectureSPA, SSR, SSG, and hybrid rendering as an architecture decision — what actually drives the choice, not a framework tutorial.
Cloud & enterprise patterns
- Cloud Design PatternsValet key, gatekeeper, competing consumers, and pipes and filters — cloud patterns this site's other architecture lessons don't already cover.
- Serverless Architecture Trade-offsCold starts, vendor lock-in, and the pay-per-execution cost model — when FaaS is the right call, and when it quietly isn't.
- Designing for Cost and Total Cost of OwnershipWhy the sticker price is the smallest part of a build-vs-buy decision, and how cost trades off against performance and reliability.
- Enterprise Architecture FrameworksWhat TOGAF's ADM cycle actually provides, and how enterprise architecture differs from solution and application architecture.