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.

Architecture styles govern the way we should build our software system. We'll revisit monolithic architectures, and then dive into components of distributed architectures.

“Microservice architecture” should not be the only buzzword in your arsenal. Let’s go one step up and look at various architectures that we may know and analyze them in the context of non-functional requirements.

There are no right answers to architecture, only trade-offs. In this lecture, we will be establishing a problem solving mindset and find strategies to justify our architecture decision-making process.

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.

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.

In this lecture we will discuss how to write a Solution Architecture Document (SAD), in prepratation for the final deliverable for this course.

Lectures from industry professionals. Topic TBD

Lectures from industry professionals. Topic TBD