• 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]

Permalink | From 28 June 2021 to 04 July 2021 | Last updated on: Thu, 11 Nov 2021 07:26:32 GMT

• Versioned Value - When a distributed system has mutable data, nodes need to know which is the most recent value, so a versioned value stores a version number with every value. more… [Martin Fowler]
• When not to use Event Sourcing? - Event Sourcing is perceived as a complex pattern that’s challenging to learn. Typically it’s matched with the financial industry or big… [Event-Driven by Oskar Dudycz]
• Lamport Clock - Next distributed system pattern from Unmesh is the Lamport Clock. Distributed systems can't assume that time is consistent between servers, and sometimes time goes backwards. Yet it's important to have some way to order events. more… [Martin Fowler]
• Stuff The Internet Says On Scalability For June 25th, 2021 - Hey, it's HighScalability time! Only listen if you want a quantum earworm for the rest of the day. Not your style? This is completely different. No, it’s even more different than that. Today in things that nobody stopped me from doing: The AWS Elastic Load Balancer Yodel Rag. pic. twitter. [High Scalability]
• Hybrid Clock - While a Lamport Clock is often necessary to order events in a distributed system, clients often need to know the actual times too. The Hybrid Clock, Unmesh's next pattern, combines these two demands. more… [Martin Fowler]
• Would you like architects with your architecture? - How to architect your organization to do architecture with or without architects. [The Architect Elevator]

Permalink | From 21 June 2021 to 27 June 2021 | Last updated on: Tue, 25 Oct 2022 17:09:04 GMT

• Event Store Conversations hosted by Yves Lorphelin - Yves Lorphelin has started a series of videos on YouTube called Event Store Conversations. Each Conversation is with a member of the Event Store team, talking about their role at Event Store or their views on Event Sourcing. [Event Store blog]
• Splitting a Domain Across Multiple Bounded Contexts - How designing for business opportunities and the rate of change may give you better contexts. I have started collaborating with Mathias Verraes and writing on the topic of Bounded Contexts and strategic design. This blog post is the first in … Continue reading → [The Responsible Designer]
• Getting started with Elixir and EventStoreDB with the Spear gRPC client - Elixir is a dynamic, functional language built on the Erlang VM. Elixir has powerful built-in abstractions for writing reactive, eventually-consistent applications, making it perfect for Event Sourcing. [Event Store blog]
• Generic does not mean Simple - As you know, I am a fan and practitioner of CQRS.. I believe that it is falsely considered as complicated. In my opinion, it can help even… [Event-Driven by Oskar Dudycz]
• Gossip Dissemination - Unmesh Joshi is completing another batch of his series on Patterns of Distributed Systems. First of these is Gossip Dissemination, which uses a random selection of nodes to pass on information to ensure it reaches all the nodes in the cluster without flooding the network more… [Martin Fowler]
• Sagas in practice - This blog is a how-to implement a Saga with Axon and Spring Boot. Saga’s are a powerful concept but, you need to think about other options before implementing a Saga. You’ll have to keep in mind that the Saga should only orchestrate the process. The business logic should be kept in the Aggregates. The usage of a Saga implies more database traffic and CPU power for serializing and deserializing the instances. A Saga uses several tables in the database to store and retrieve its state. If you don’t need it, I recommend using a stateless event handler instead. [Axon Framework and related blogs via Aggregater Linklog]
• Giant Leaps Rarely Happen - Success comes in small dosages. [The Architect Elevator]

Permalink | From 14 June 2021 to 20 June 2021 | Last updated on: Tue, 25 Oct 2022 17:09:04 GMT

• How do I migrate to Event Store Cloud? - Event Store Cloud has been released, and you may be wondering how to migrate your existing EventStoreDB database to the cloud. Read on to find out the ways in which we can help. [Event Store blog]
• The many ways to connect to Event Store Cloud - Event Store Cloud was built with rock solid Production stability and security in mind; as such, it uses TLS between any external connection and the API. We've created four different ways to connect to Event Store Cloud: the API, the Console UI, the CLI and Terraform [Event Store blog]
• Event Store Cloud has entered GA - We are delighted to announce that Event Store Cloud has entered General Availability (GA) and is Production Ready. [Event Store blog]
• The Features of Event Store Cloud - Event Store Cloud has entered General Availability (GA), and now is the perfect time to consider migrating to Event Store Cloud. There are a wealth of new features (discussed below) and solid reasons for analysing your infrastructure and planning your migration today. A hosted solution Event Store Cloud is a multi-cloud hosted solution, and provides a range of benefits: Scalable resources instantly allocate more resources where needed with minimal fuss. Improved backup and disaster recovery a hosted solution is safe from physical damages and accessible anywhere, making disaster recover or pandemic planning much easier. Always-available connectivity the data can be accessed from anywhere, at any time. Migration made easy there's a Replicator tool to help manage the migration to Event Store Cloud. No need for physical storage space save space in your rack and reduce server load. Production ready With a hosted Event Store, you can be assured that the version of EventStoreDB will be secure, stable and robust, and has the feature set to match. These features are all important, useful features that have been planned for some time, and the Engineering team are delighted to have them integrated into Event Store Cloud. As this represents a leap forward in the usability of the product, it’s a good idea to talk further about the new features, how they work and how they can help Event Store Cloud users. [Event Store blog]
• Saga and Process Manager - distributed processes in practice - What can go wrong with distributed systems? Everything! I like to compare distributed systems to Rocky Balboa fighting the last round with… [Event-Driven by Oskar Dudycz]
• Sponsored Post - Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte [High Scalability]
• Linux Kernel vs. Memory Fragmentation (Part I) - This post introduces common methods to prevent Linux memory fragmentation, the principle of memory compaction, how to view the fragmentation index, etc. [High Scalability]
• Event Store Replicator - After customers started using Event Store Cloud, we began receiving questions about migrating their existing databases to the cloud. Back then, we didn't have an answer to that question, although we expected it. [Event Store blog]
• Structural Typing in TypeScript - When we talk about typing in programming languages, we usually divide it into static and dynamic. Static typing is checked at the compile… [Event-Driven by Oskar Dudycz]
• Splitting a Domain Across Multiple Bounded Contexts - Imagine a wholesaler of parts for agricultural machines. They’ve built a B2B webshop that resellers and machine servicing companies use to order. In their Ubiquitous Language, an Order represents this automated process. It enables customers to pick products, apply the right discounts, and push it to Shipment. Our wholesaler merges with a competitor: They’re an older player with a solid customer base and a huge catalog. They also have an ordering system, but it’s much more traditional: customers call, and an account manager enters the order, applies an arbitrary discount, and pushes it to Shipment. [Mathias Verraes]
• Implementing event sourcing using a relational database - Event sourcing is a pattern in which a stream of events constitutes the primary source of truth in a system. These events capture facts — state changes that occur to the entities and aggregates in our system — and hence are immutable. On the technical level, event sourcing can be implemented using dedicated storage systems, as well as general-purpose "NoSQL" and SQL databases. [SoftwareMill via Aggregater Linklog]

Permalink | From 07 June 2021 to 13 June 2021 | Last updated on: Sat, 28 Aug 2021 19:54:33 GMT