搞笑談軟工

Event Sourcing (19): Implement optimistic locking in InMemoryRepository

July 26 15:52~16:39 ▲Figure 1: Optimistic lock test case foreword This series of articles was originally written by Teddy in order to create a course example of [ Event Sourcing and Command Query Responsibility Separation Architecture Implementation Class ]. The course example has been completed, and the serialization of this series of articles has ended. …

Event Sourcing (19): Implement optimistic locking in InMemoryRepository Read More »

“Clean Architecture Implementation: Getting Your Hands Dirty on Clean Architecture” Code Analysis

July 19 09:07~10:58 ▲Figure 1: ” Get Your Hands Dirty on Clean Architecture ” program example directory structure foreword In September 2021, Teddy wrote a book review for the book ” Get Your Hands Dirty on Clean Architecture ” (please refer to < [One less book] Get Your Hands Dirty on Clean Architecture >). A …

“Clean Architecture Implementation: Getting Your Hands Dirty on Clean Architecture” Code Analysis Read More »

Event Sourcing (18): Implementing Idempotent

July 9 14:20~16:20 ▲NotifyBoard implements Idempotent architecture diagram foreword Teddy introduced why Event Handler needs to have Idempotent in <Event Sourcing (16): Event Semantics and Idempotent in Distributed Systems>. This episode takes the Event Handler—NotifyBoard that generates GetBoardContent in the ezKanban system as an example (please refer to <Event Sourcing (10) ): Implement Projector >), …

Event Sourcing (18): Implementing Idempotent Read More »

Event Source (17): Read the events stored in the hand-carved Event Store

July 7 18::09~19:21; 21:15~23:23; July 8 13:45~16:27 ▲Store Checkpoints in the Event Store foreword Although using EventStoreDB, a database specially designed for Event Sourcing and CQRS, can reduce a lot of development work, in practice developers may only use relational databases due to company requirements or project constraints. In this case, you must simulate the …

Event Source (17): Read the events stored in the hand-carved Event Store Read More »

Event Sourcing (16): Event Semantics and Idempotent for Decentralized Systems

July 6 23:14~24:00; July 7 00:00~01:39 ▲I’m almost exhausted XD foreword The reason why villagers use Event Sourcing and CQRS is to develop microservices in many cases. The microservice architecture is a distributed system. Compared with the centralized system, the distributed system has the characteristics of heterogeneity, easy expansion, robustness, high fault tolerance and low …

Event Sourcing (16): Event Semantics and Idempotent for Decentralized Systems Read More »

Event Sourcing (12): Snapshots to Accelerate Aggregate Reads

Original link: https://teddy-chen-tw.blogspot.com/2022/07/12.html July 04 21:23~23:39 ▲Figure 1: Using snapshots to accelerate Aggregate read speed foreword The Event Sourcing system is very simple and fast on the writing side, but reading because it needs to use all the domain events to which the Aggregate instance belongs to get the latest status one by one, it …

Event Sourcing (12): Snapshots to Accelerate Aggregate Reads Read More »