Latest news and articles about DDD, CQRS, Event Sourcing and Software Architecture in general, aggregated daily and delivered weekly to your feed (RSS) reader. Subscribe here!

Week 24, year 2021

  • 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