Week 26, year 2021
- Version Vector - A Lamport Clock is effective to order events on a single server, but with multiple servers we need a vector of version numbers to detect concurrent updates. more… [Martin Fowler]
- Sponsored Post - Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte [High Scalability]
- Stepping Back from Speaking - A personal note on why I wish to give up doing talks more… [Martin Fowler]
- How to get the current entity state from events? - Today I’d like to go back a bit to the basics of Event Sourcing. I recently realised that I often cover more advanced topics. So sometimes… [Event-Driven by Oskar Dudycz]
- Follower Reads - When you are using Leaders and Followers, you can use Follower Reads to achieve better throughput and lower latency. However there is always a replication lag between the leader and the followers, so you may need to take action to preserve consistency. more… [Martin Fowler]
- 21.6.0 Release Notes - We are pleased to announce the official release of EventStoreDB 21.6.0 for the following operating systems: [Event Store blog]
- Counterexamples regarding consistency in event sourced solutions (Part 1) - Some mistakes can easily be prevented, by knowing how to avoid them. Some things may seem implicit and obvious to some people, while seeming esoteric and opaque for others. Software is hard and involves hard problems, and there is so much to learn; I write this with compassion and respect for developers currently in the situations I might describe in these posts. [Event Store blog]
- photostream 126 - Bacharach, Rhineland-Palatinate, Germany (2016) [Martin Fowler]
- Counterexamples regarding consistency in event sourced solutions (Part 2) - In Part 1 the introduction talked about certain blind-spots we may have, when getting into event sourcing. We also covered the first of five counter-examples, namely 'confusing timelines in the processing of events'. [Event Store blog]
- Counterexamples regarding consistency in event sourced solutions (Part 3) - In Part 2 we looked at two counterexamples, one related to failing projections, and another about how not to propagate domain events. [Event Store blog]
- Thinking in Events: From Databases to Distributed Collaboration Software - In this keynote I give a subjective but systematic overview of the landscape of distributed event-based systems, with an emphasis on two areas I have worked on over the last decade: large-scale stream processing with Apache Kafka and associated tools, and real-time collaboration software in the style of Google Docs. [Martin Kleppmann via Aggregater Linklog]