Top all-time · #6356
Kurrent
Company blog · eventstore.com/blogprogrammingdatasystems
Kurrent is the company blog at eventstore.com, writing about programming, data and systems. Since 2020, 13 different Hacker News readers have linked it 15 times, most often “Beginner's Guide for Event Sourcing”. It is still writing: the last post was on 2026-08-20, and you can follow it by feed.
Too few sampled comments (10) to say how often HN recommends it.?
Why HN links it
HN readers link eventstore.com for event sourcing material, such as a post on GDPR compliance via crypto shredding, and for customer case studies and the EventStoreDB product pages.
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.
Kurrent is the only event-native database that preserves history, streams changes, and powers agentic AI — trusted by 10,000+ companies. Start free, no credit card required.
Most-linked posts?
- /3 people · 3 mentions · first linked 2021-08-12
- /2 people · 2 mentions · first linked 2020-04-27
- Beginner's Guide for Event Sourcing2 people · 2 mentions · first linked 2021-11-30
What Hacker News says?
Thanks for answering! The bar is as I described. The events are the source of truth, only if you're using them in the write model as a basis for the state rehydration. If you're using materialised view, even though it's built based on events, then you outsourced the truth to other storage. If you're doing a pattern that you're just using events to build up the materialised view you use for the write model logic, tha…
Comment linking /blog/snapshots-in-event-sourcing
on “Event Sourcing Is Hard (2019)”Submitted EventStore Cloud – Managed EventStoreDB clusters in the cloud as a story · 11 points
HN discussionCould you provide an exact quote? I haven't been able to find any usage of "populate". I found: `the raw event stream subscription setup kills the ability to locally reason about the boundaries of a service.` `you have to talk to the people who will be consuming the events you produce to ensure that the events include enough data for the consuming system to make a decision` `wire a fleet of services together via an…
Comment linking /event-sourcing
on “Event Sourcing Is Hard (2019)”Submitted Event Immutability and Dealing with Change as a story · 9 points
HN discussionAn Event-sourced system can be compliant with GDPR, with crypto shredding: https://www.eventstore.com/blog/protecting-sensitive-data-in...
Comment linking /blog/protecting-sensitive-data-in-event-sourced-systems-with-crypto-shredding-1
on “Event Sourcing Is Hard (2019)”Submitted Beginner's Guide for Event Sourcing as a story · 3 points
HN discussionhttps://www.eventstore.com/case-studies/insureon I can attest to this case study being 100% true. Our platform has been using EventStore as our primary database for 9 years going strong, and I'm still very happy with it. The key thing is that it needs to be done right from the very beginning; you can't do major architecture reworks later on and you need an architect who really knows what they're doing. Also, you can…
Comment linking /case-studies/insureon
on “Anti-patterns in event-driven architecture”Submitted Snapshots in Event Sourcing as a story · 2 points
HN discussionWhat's wrong with EventStore? https://www.eventstore.com/
Comment linking /
on “Event Sourcing (2005)”Submitted Event Store Secures Series A Investment as a story · 2 points
HN discussionWe used EventStore [0] as an Event Store in a previous project (yes, this does get tedious to explain). I'm quite curious who this is aimed at. .NET shops are often so deeply invested in the Microsoft ecosystem. In that previous project, needing to run/administer PostgreSQL instead of SQL Server would have been a significant administrative detriment to getting the project greenlit. (The fact that EventStore doesn't…
Comment linking /
on “.NET Transactional Document DB and Event Store on PostgreSQL”One way to deal with this is to divide up your event streams into small streams - say one per order. Those small streams then may be aggregated into a larger stream so that you can just process events for all the orders together, for example. If you hit a poison message, block just that smaller stream, not the aggregated larger stream. Once you fix the problem, reprocess the entire small stream starting from the poi…
Comment linking /
on “Queue Despair: Ordering and Poison Messages”Have you considered backing your application's state-synchronization with a centralized CQRS/ES event store (e.g. https://www.eventstore.com/ )? You get the same semantics, without paying the overhead of building them on top of a CRDT abstraction; and the event store itself also "knows" (in the sense that it supplies the framework and you supply the logic) how to reduce over states in order to build snapshot states…
Comment linking /
on “You might not need a CRDT”Event Store Ltd | Full time | Remote Event Store Ltd is a company that develops EventStoreDB, a stream database built for Event Sourcing, and offers consultancy and support services worldwide for businesses looking to implement Event Sourcing within their systems architecture. We are hiring for several roles in our Engineering and Developer Advocacy teams https://www.eventstore.com/careers
Comment linking /careers
on “Ask HN: Who is hiring? (February 2023)”If what you are looking for is a DB-like application, I recommend: https://eventstore.com/ Not sure if you can set retention periods, but it is definitely worth to take a look into that, and definitely a good starting point.
Comment linking /
on “Ask HN: Where to Store My Events?”
