Discovery and requirements
Learn to identify what you're building and what could go wrong.
Course summary
Use this page to revisit what each stage gives you and return to the exact weak point that needs another pass.
Stage 1 of 3
Start from what architecture is for, and how to think about components, boundaries and responsibilities in small systems.
Learn to identify what you're building and what could go wrong.
Document and communicate architectural decisions using C4 models, Architecture Decision Records, API contracts, and security by design principles.
Write secure, maintainable code with proper input validation, output encoding, session management, error handling, and supply chain security.
Ensure quality and security through comprehensive testing strategies, OWASP ASVS integration, accessibility testing with WCAG 2.2, and performance testing.
Automate secure deployments with CI/CD pipelines, DevSecOps integration, deployment strategies, and Infrastructure as Code basics.
Run systems reliably in production with Google SRE principles, four golden signals, observability triad, and effective incident response.
Master troubleshooting tools and techniques using OSI layers, browser DevTools, command-line diagnostics, and TLS certificate inspection.
Evaluate systems across quality attributes including security, privacy, accessibility, performance, reliability, scalability, maintainability, and more.
Now that you have worked through all eight modules, it is time to test your understanding.
Stage 2 of 3
Layered patterns, microservices, events, data ownership and real trade offs between coupling, performance and changeability.
The big styles are patterns, not rules.
Systems talk in two main ways.
latency and throughput are easy to measure.
State hides everywhere.
Stage 3 of 3
Event driven systems, CQRS, integration patterns, observability and digitalisation strategy across whole organisations.
Glossary Tip.
Glossary Tip.
Caching helps, but it creates new risks.
Glossary Tip.