Data architecture for solution architects
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
explain what a solution architect owns in data architecture and what is left to specialists.
Planned topics
- You decide where each data set lives, who owns it, how it moves, and how long it stays; a data engineer decides how to tune the pipeline.
- Every data set needs one system of record: the one place whose version wins in a dispute.
- Data architecture is a view of the pack, next to the context, container, and deployment views.
- Decisions here outlive the application: reports and audits read today's data for years.
Draft outline details
Demonstration
a table of Larkspur data sets (customers, products, prices, stock, orders, payments, returns) with empty columns "system of record", "consumers", "retention" to be filled during the module.
Check your understanding
What is a system of record?
Show answer
The single system whose copy of a data set is authoritative when copies disagree.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.