Make foundations for event-sourcing / activities

[moul]

Inspiration:

• https://github.com/z0mbie42/goes
• https://stackoverflow.com/questions/7065045/using-an-rdbms-as-event-sourcing-storage
• http://scottlobdell.me/2017/01/practical-implementation-event-sourcing-mysql/

---

Questions:

• pros / cons ?
• how?

[moul]

Additionally we can use a pubsub broker Example: https://github.com/IAmMorrow/grpc-pubsub-broker See #8

[moul]

Interesting article: https://medium.com/@shijuvar/building-microservices-with-event-sourcing-cqrs-in-go-using-grpc-nats-streaming-and-cockroachdb-983f650452aa

[moul]

First version will be simple -> only log write (append events in db)

This way we will already be able to have a "user activity" view per user, and will defer the rest of the event-sourcing/CQRS implementation for later

the most important part of event-sourcing is actually to log the events, so let's start right now! :)

[moul-bot]

➤ Manfred Touron commented:

Dummy means -> log activities , will see for the rest later