Tweet

Jérémie Chassaing

17 Dec, 4 tweets, 2 min read

My #fsadvent post is up:
Functional Event Sourcing Decider
thinkbeforecoding.com/post/2021/12/1…
At last, a full length blog post about functional #eventsourcing
#fsharp

@sergey_tihon

@sergey_tihon here it is.

This is a long post based on my upcoming book about Functional Event Sourcing. Not ETA yet, but I thought I still needed to publish something at some point. There is of course far more content in the book 😁

And there are probably more post that will follow

• • •

Missing some Tweet in this thread? You can try to force a refresh

This Thread may be Removed Anytime!

Twitter may remove this content at anytime! Save it as PDF for later use!

More from @thinkb4coding

Jérémie Chassaing

@thinkb4coding

4 Sep

@johnbywater

@johnbywater @SKleanthous @RagingKore That was a long interesting thread :) and there are many things to discuss here.
After discussion with Eric and other DDD practitioners, the tactical patterns are very concrete, but come from more abstract ideas.

@johnbywater

@johnbywater @SKleanthous @RagingKore The aggregate is implemented as a class that references other entities and value objects to maintain consistency. But the more general description is that this is something that is defined by a consistency boundary. What is inside is consistent, what's outside *doesn't have to*

@johnbywater

@johnbywater @SKleanthous @RagingKore Once this is said, an aggregate should not have to call another's method aggregate as part of it's own decision. (or they would become consistent together, and be a single aggregate).

Read 28 tweets

Jérémie Chassaing

@thinkb4coding

10 Jul 20

After several discussions about event sourcing today, I think it's time to clarify things. Thread ⬇ 1/8

When talking about Query eventual consistency, views autorebuild with 0 downtime deployment, snapshots, automatic failover, we're in the Advanced Non Functional Requirements column with high availability, low latency, distributed systems, so infra is advanced and non obvious 2/8

This is normal, you cannot have high quality of service under scale and hope it will work like magic. You'll have to solve some problems, and all solutions will not be obvious. Distributed systems are hard. 3/8

Read 9 tweets

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Share this page!

Jérémie Chassaing

Try unrolling a thread yourself!

More from @thinkb4coding

Jérémie Chassaing

Jérémie Chassaing

Did Thread Reader help you today?

Like this author's thread?