A very interesting article that I find very useful! Here are shared some of the common producer models, which show how to transform a classic architecture to an Event Sourcing model.
Below is the link to the complete article!
In part one, we learned about how at Nordstrom we’ve been exploring and implementing event-sourcing as an architectural pattern. In part…
Source: Event-sourcing at Nordstrom: Part 2
Here a scort preview of patter
![](https://miro.medium.com/max/1272/1*TrcKoZ3_tTrv0MbdvFI12A.png)
Produce directly to the ledger at the moment of the event
![](https://miro.medium.com/max/1400/1*XhZQPGW06zJXUNTvkJPSvw.png)
Transform an existing stream
![](https://miro.medium.com/max/1400/1*duQ_qg4z0qTPEAL9U3CB7A.png)
Write-through a database and use change data capture
![](https://miro.medium.com/max/1400/1*z9mXE2HQAW0M6dUlNpwIdQ.png)
Poll an existing request/response service for changes and publish
![](https://miro.medium.com/max/1400/1*LNFJ6IDviPkNf7s2HnYU0Q.png)
Subscribe to a web socket or pub/sub
![](https://miro.medium.com/max/1400/1*ctEJNXVaqwdrrxeLf-SkGw.png)
Streamify batches of data
![](https://miro.medium.com/max/1400/1*lPtS5iZGLrelPigf-_5-gw.png)
Use event triggers in your serverless ecosystems
![](https://miro.medium.com/max/1400/1*IW-rxvLxLKWn5rlu28fDFw.png)
Watch for event-worthy actions in react/redux
![](https://miro.medium.com/max/1400/1*HmR8-DwbqLhEAxmSOgK_bg.png)
Replicated table from an occasionally offline client
Recent Comments