episode/event-sourcing-and-materialized-view/ #943
Replies: 1 comment
-
Want to join in the discussion? You can do that in two ways! You can either authorize the giscus app to post on your behalf using the GitHub OAuth flow. Alternatively, you can comment in GitHub Discussions directly if you'd prefer not to grant access to the giscus app. Please keep the discussion on topic with the post. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
episode/event-sourcing-and-materialized-view/
The event sourcing pattern is a well-known pattern and has been around for some time. The idea is that you use an append-only store to record the full series of actions taken on the data. This combines well with the materialized view pattern, where a pre-populated view is generated over one (or more) data stores when the data isn't in an ideal format for querying. These two patterns are common patterns used in an event-driven architecture. Join Chris and Steph as they talk about both of these patterns and how they may be able to help. This is another episode in the series of Architecting for the Cloud, one pattern at a time.
https://www.cloudwithchris.com/episode/event-sourcing-and-materialized-view/
Beta Was this translation helpful? Give feedback.
All reactions