Schedule

Introduction to course structure, the fundamentals of large software systems, and how to effectively contribute to large software systems.

Understanding the architecture of large codebases and recognizing real-life applications of design patterns in a large codebase.

What does it mean for a system to be performant? What are the operational requirements that we need to consider when designing a software system?

Considerations to ensure the code quality of the system to enable it to be operated and maintained in quality.

A picture is worth a thousand words. Visualizations are one of the most powerful tools in an architect's belt. This lecture discusses how diagramming and whiteboarding can be used to augment the communication that ensures software projects succeed.

The lecture covers forming an architecture for large software systems, discussing application architecture patterns, the transition from monoliths, and service-oriented architecture. It highlights maintainability, testability, layered architecture styles like MVC, and the microkernel architecture style. The lecture also examines trade-offs in distributed architectures, including latency and network reliability.

This lecture covers various distributed architectures, including pipeline, broker, and mediator topologies, and their application in report generation and AI. It also differentiates between operational and analytical data, discussing data warehousing, data lakes, and data mesh approaches.

Lectures from industry professionals. Topic TBD

A good architecture takes into account usage patterns. Explore some of the creative ways the industry uses to solve architecture challenges.

Architecture is about communication and decision making. This lecture covers how architects analyze architectural risk in order to determine which decisions needs to be communicated to the rest of the team.

TBD

TBD