Cloud Native Programming with Golang

Events sourcing

The basic idea behind event sourcing is that instead of fully relying on a local database to read the state, we need to make use of a recorded stream of events to form the state. To make that work, we will need to store all current and past events so that we can retrieve them at a later time.

We need an example to solidify this theoretical definition. Let's say that the support service had failed and crashed before it could receive the new customer event. If the support service doesn't use event sourcing, then when it restarts, it will not find the customer information in its own database and will never know about the customer. However, if it uses event sourcing, then instead of only looking at its local database, it will ...