Template description
OLTP is the only shared source, and it splits immediately. One arrow enters Change stream, then Streaming job, then Serving DB, then Real-time API. The other arrow enters Daily snapshot, then Data lake, then BI dashboard. Nothing connects the lake to the API, and nothing connects Serving DB to the dashboard. The stream path exists so a read can see a change without waiting for the night. The snapshot path exists so reporting can scan history that a serving store is not meant to keep. The two consumers are fresh operational reads and historical reporting, and this drawing refuses to mix them.
When to use it
Open it when an API incident is being debugged from a dashboard that reads the lake, or when someone proposes to point the real-time API at the daily snapshot. The split explains why those numbers are allowed to disagree until the snapshot catches up.
How to adapt it
Rename OLTP, Serving DB, and Data lake to your systems, and change Daily snapshot if the batch is hourly. Add a lake-to-serving arrow only if you truly rebuild the serving store from the lake. If the API must expose history, give it a separate store rather than quietly linking it to the dashboard path. Name the change stream technology only if the team already shares that word.