David Stevenson’s Reviews > Reactive Design Patterns > Status Update

Finished… final read through the last Appendix is a copy of the Reactive Manifesto. No doubt there are parts of it that I have a greater understanding and appreciation for now, having read this book. Want to spend some more time and play with the source code samples more.

Final patterns covered are Event Sourcing and the Event Stream. The Event Sourcing pattern notes the point I noticed myself earlier in the chapter about the Events being outside of the Domain Object, but at this point notes that the Events do belong within the domain, bringing me to a content state. One consideration not mentioned here is whether to expose your internal events externally or not.

The Domain Object pattern presented is interesting. The events here are emitted by the encapsulating actor, rather than from within the domain object itself - so, akin to a response, which I tend to think is different to an event. But this is a detail; the pattern itself I like a lot.
Then, there was an intro to the Sharding pattern. Example code is a little tricky but one gets the picture.

The Throttle pattern covered; gonna study the code in more detail. Next is the Domain Object pattern, something that appeals to me as a DDD person, but was interested to read another reactive book where the authors suggested keeping domain logic directly in the actor code. The Domain Object pattern is attractive to me, from a testing perspective, so the design seems “nicer” this way.

The Drop pattern - interesting stuff about what you can do when your system is pushed to its limits

Saga, Business Handshake patterns. A few short chapters to go, the remainder looks interesting!

Forward Flow (nice) and Aggregator patterns covered. Had not though of Forward Flow before but nice concept explained very simply here. Also can be related back to resource management patterns too.