Top all-time · #3760
Udi Dahan
Personal blog · udidahan.comprogrammingsystems
Udi Dahan's personal blog at udidahan.com covers programming and systems. Since 2009, 21 different Hacker News readers have linked it 23 times, most often “Clarified CQRS”. The last post was in 2016, but the archive is still widely read.
Too few sampled comments (10) to say how often HN recommends it.?
Why HN links it
HN readers cite Udi Dahan's posts as sources on CQRS, event sourcing, service bus versus broker, and not deleting data. One commenter calls his blog and presentations great.
Summarised by Claude from a sample of 10 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Clarified CQRS2 people · 3 mentions · first linked 2012-03-07
- Don't Delete – Just Don't (2009)2 people · 2 mentions · first linked 2021-09-27
- /2011/03/24/bus-and-broker-pubsub-differences/2 people · 2 mentions · first linked 2013-12-22
What Hacker News says?
You mean they follow what many people consider best practices? https://softwareengineering.stackexchange.com/questions/1592... https://stackoverflow.com/questions/820466/never-delete-entr... https://serverfault.com/questions/31455/should-i-ever-delete... https://www.infoq.com/news/2009/09/Do-Not-Delete-Data http://udidahan.com/2009/09/01/dont-delete-just-dont/ https://stackoverflow.com/questions/2549839/are-soft-del…
Comment linking /2009/09/01/dont-delete-just-dont/
on “Facebook Secretly Saved Videos Users Deleted”Submitted Don't Delete – Just Don't (2009) as a story · 3 points
HN discussionEventSourcing/CQRS (Command/Query Responsibility Segregation) is gaining a bit of traction in the .NET community. There are some great presentations[1], blogs[2][3] and projects[4] related to this architecture. [1]: http://www.infoq.com/presentations/Command-Query-Responsibil... [2]: http://www.udidahan.com/?blog=true [3]: http://blog.jonathanoliver.com/ [4]: https://github.com/joliver/EventStore/
Comment linking /?blog=true
on “Now that people are considering NOSQL will more people consider no-DB”Submitted It’s not about you as a story · 3 points
HN discussionI think CQRS is more commonly viewed as an architectural pattern, not a code pattern, despite many definitions floating out there on the internet that focus on command/query object patterns. See this post: http://udidahan.com/2009/12/09/clarified-cqrs/ . If we view it as an architectural pattern, it becomes folly to think that CQRS can be distilled into a library.
Comment linking /2009/12/09/clarified-cqrs/
on “Building a CQRS/ES web application in Elixir using Phoenix”Submitted Clarified CQRS as a story · 3 points
HN discussionIf you have an aggregate root, it is responsible for knowing when changes to the aggregate have occurred, and thus making those visible. What is the mechanism for it to do so? Does the aggregate root retain the events and decide when to dispatch them (likely after successful persistence to a datastore)? Once ready for dispatch, what do you use to handle the events? Some kind of DomainEvents class ala https://udidaha…
Comment linking /2009/06/14/domain-events-salvation/
on “Show HN: I wrote a book on implementing DDD, CQRS and Event Sourcing”Submitted Clarified CQRS (2009) as a story · 2 points
HN discussionNow that's a reassuring yes :) What I meant is it seems (I've never used or seen it before) to be closer to a message broker than a bus - http://www.udidahan.com/2011/03/24/bus-and-broker-pubsub-dif...
Comment linking /2011/03/24/bus-and-broker-pubsub-differences/
on “Avoiding Event Chains in Single Page Applications”Submitted Don’t Delete – Just Don’t (2009) as a story · 2 points
HN discussionI really like this. Has some overlap with Command-Query Responsibility Segregation, which I have found very useful: http://www.udidahan.com/2009/12/09/clarified-cqrs/
Comment linking /2009/12/09/clarified-cqrs/
on “Runaway complexity in Big Data... and a plan to stop it”Submitted The Fallacy of ReUse (2009) as a story · 1 points
HN discussionYou don't really control the composition that closely. The whole point of having a lot of microservices is that you can update and work on very isolated functionality at a time distributed. As other people have noted as well in here, you should always keep the interface backwards compatible, if needed make a second version of the API or the messages, but never really have to deploy more than a couple of services who…
Comment linking /training/
on “Ask HN: How do you version control your microservices?”Submitted The Fallacy of ReUse as a story · 1 points
HN discussionI still feel the canonical answer to "what should my default data management policy in write-some-read-a-ton situations" is to, at write time: 1) store an appropriate write-whole/data-mining-friendly format 2) ASAP, for each major view, write out a Redis-style O(1)-to-read data structure 3) think carefully about backup and replay strategies You trade a slightly stale read of the very hottest data for much improved p…
Comment linking /2009/12/09/clarified-cqrs/
on “Antirez: You Need to Think in Terms of Organizing Your Data for Fetching”Submitted Don't Delete – Just Don't (2009) as a story · 1 points
HN discussionThats because NServiceBus is a Service Bus and not a broker: http://www.udidahan.com/2011/03/24/bus-and-broker-pubsub-dif... For HA you simply run a distributor process for each logical event on windows cluster and add as many worker nodes as you see fit. Because NServiceBus uses the store and forward pattern if a NServiceBus process/machine hosting it goes down, you are still guaranteed the eventual delivery of mes…
Comment linking /2011/03/24/bus-and-broker-pubsub-differences/
on “Thank you Microsoft, and so long”Submitted UI Composition Techniques for Correct Service Boundires as a story · 1 points
HN discussionThis is relevant to the discussion: - http://udidahan.com/2007/12/29/wcf-everywhere-not-on-my-watc... (MS SOA technology) - http://www.oracle.com/technetwork/issue-archive/2015/15-mar/... - Also this: http://stackoverflow.com/questions/25501098/difference-betwe... - http://service-architecture.blogspot.co.at/2014/03/microserv...
Comment linking /2007/12/29/wcf-everywhere-not-on-my-watch/
on “Ask HN: Any veteran feedback from the SOA era?”Submitted Dont try to model the real world - it doesnt exist as a story · 1 points
HN discussionSubmitted On Design for Testability as a story · 1 points
HN discussionSubmitted MySpace Architecture Considered Expensive as a story · 1 points
HN discussionSubmitted The Fallacy Of ReUse as a story · 1 points
HN discussion
