Operational vs analytical workloads
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
show why transaction processing and reporting need different stores.
Planned topics
- Operational (OLTP): many small reads and writes, milliseconds, current state; a till sale must never wait.
- Analytical (OLAP): few huge scans and aggregations over history; a quarterly margin query touches millions of rows.
- Running both on one database lets a report slow down checkout and a schema change break the report.
- The bridge is a copy: replicas, change capture, or pipelines feed a separate analytical store.
Draft outline details
Demonstration
a two-column table, OLTP vs OLAP, with rows for access pattern, data shape, freshness, users, typical store, and a Larkspur example in each (basket write vs "margin by region by week").
Check your understanding
Why not point the board dashboard at the order database?
Show answer
Heavy scans compete with checkout, and report needs shape the schema badly; use a separate analytical copy.
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.