Discover and read the best of Twitter Threads about #eventsourcing

Most recents (3)

@HaripraghashS @HaripraghashS 2 short questions without 2 short answers ­čśůBut let's try! Projections for me when I started my journey with #EventSourcing was the hardest thing to understand. I thought: ok, I can rebuild the aggregate state by replaying events one by getting them by id 1/
@HaripraghashS Having that I'll have the state of the single aggregate. Wait a minute! If I won't to do that for the aggregate list then I'd need to get all events for those aggregates and reply it one by one? Nah that's can't be! For that we have we have projections. As you for sure know /2
@HaripraghashS What are projections? It's just representation and interpretation of the set of event. What's more when we're replying events to get aggregate state - that's also projection. It's easy to forget about that because it's default case. We're just interpreting events to get state /3
Read 17 tweets
Bir yaz─▒l─▒m geli┼čtiricinin bilmesi gerekenlerle ilgili 15 maddelik flood geliyor.. M├╝mk├╝n oldu─čunca fazla keyword├╝ bir araya toplamaya ├žal─▒┼čt─▒m.
Hadi Ba┼čl─▒yoruz!

#Developer #Software #Java #code #kod #yaz─▒l─▒m #development #computer #bilgisayar #tool #PC #IT #web #tech #data
1-Temel veri yap─▒lar─▒ (linkedList, map, tree vb) ve temel algoritmalar (s─▒ralama, arama vb)

S─▒f─▒rdan kodlama ihtiyac─▒n─▒z b├╝y├╝k ihtimalle hi├ž olmayacak. Ancak ihtiya├ž an─▒nda do─čru yerde do─črusunu se├žebilmek i├žin o veri yap─▒s─▒n─▒n veya algoritman─▒n nas─▒l ├žal─▒┼čt─▒─č─▒n─▒ bilmeniz ┼čart
2- Network Temelleri

OSI Modelini ve 7 katman─▒; temel protokolleri(#TCP-IP, TCP-UDP, #HTTP, #FTP), g├╝venlik protokollerini(#HTTPS, #SFTP, #SSL), monitoring protokolleri(#SNMP, ICMP) bilmekte fayda var. Ayr─▒ca a─č ekipmanlar─▒n─▒n g├Ârevlerini tan─▒mak ve 7Layer yerlerini bilmek laz─▒m
Read 16 tweets
I feel very sad about this, but I am compelled to comment. This article does such a great disservice to #DDDesign #CQRS and #EventSourcing that if my platform/toolkit/framework where cited in it, I'd demand removal:

The software industry is continuously exposed to such poor literature and guidance. The term "domain model" should not even be used here, nor "domain event." Even so, the whole article is flawed. Please don't follow this advice.
Unfortunately this article argues "accidental complexity" as a reason to change the "domain model" and then goes about introducing heaps of unnecessary complexity. This appears to be an effort in showcasing a framework rather than simplifying the solution.
Read 3 tweets

Related hashtags

Did Thread Reader help you today?

Support us! We are indie developers!


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

Become a Premium Member ($3.00/month or $30.00/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 Become our Patreon

Thank you for your support!