Almost every system lives or dies by how it handles data. The way you store, model, and move data shapes performance, consistency, cost, and how easily the system can change. This module looks at data from the architect's point of view: which data stores fit which problems, and how data flows through the organisation.
You'll start by comparing SQL and NoSQL databases and learning how to choose between them. Then you'll look at CQRS, a pattern that uses separate models for reading and writing data when their needs differ. Finally, you'll follow data out of the transactional system with ETL data pipelines and see where it ends up in a data warehouse, data lake, or lakehouse for analytics.
Next up is Distributed Systems & Integration, where you'll see how services share data and communicate reliably across a network.
How SQL and NoSQL compare for system design and real application architecture, and how to choose the right database for structured and semi-structured data.
Command Query Responsibility Segregation is a design pattern that treats retrieving data and changing data differently, and this lesson explains how it works.
How ETL data pipelines extract data from various sources, transform it, and load it into a centralised store for analysis.
A simple explanation of what a data warehouse, data lake, and data lakehouse are, and how they differ, alongside ETL and OLAP vs OLTP.