15 Comments

The way you architect your data model is the most critical part of any system. There are many proven ways to do it, but I believe the best way is to use event sourcing.

Great article, Raul!

Expand full comment

That's a good point, Petar.

The data architecture will affect scalability and performance down the road.

Expand full comment

This is a wonderful explanation of Event Sourcing, Raul!

Also, thanks for the mention.

Expand full comment

Thanks, Saurabh!

Expand full comment

Love this breakdown, what an amazing solution! It adds complexity, but comes with much power.

Thanks for the shoutout my brother.

Expand full comment

Exactly, Daniel, complexity is the main the main trade-off.

Thanks!

Expand full comment

I never thought about using the history of events as data to predict the future. Right now the information we have at hand is super valuable to make the most of AI

Expand full comment

It is just an idea ;)

Thanks, Fran.

Expand full comment

Great article to learn about event sourcing.

Also, thanks for the mention Raul!

Expand full comment

Thanks, Ashish!!!

Expand full comment

Great article Raul. And thanks for the mention

Expand full comment

Keep those coming, Riccardo!

Expand full comment

A powerful pattern when you need strong audit logs, fantastic write.

Expand full comment

Yes, one of the significant benefits.

Thanks, Neo!

Expand full comment

I never really thought about event based systems as a system of record that I can use to

move forward or backward and understand state transitions to be honest, but I love the idea and specially of mixing that with AI. But I gotta ask, if your sole purpose of using events is this, wouldn’t blockchain be more suitable?

Expand full comment