Week 40, year 2017
- Why we Avoid Putting Value Objects in Events - What’s the harm in putting Value Objects in your Events? Say we have the following event: public class PlannedNewRoastDay : Message { public readonly Guid Id; public readonly string RoastDate; public PlannedNewRoastDay(Guid id, string roastDate) { Id = id; RoastDate = roastDate; } } [Nick Chamberlain on Nick Chamberlain]
- Event Sourcing example application - This is code example for a simple Event Sourcing and CQRS application using Javascript. [Serialized development blog]
- A simple ToDo app - We have created a small ToDo application do demonstrate how to use our API:s to build a CQRS/EventSourcing application [Serialized development blog]
- DDD Weekly: Issue #44 - What Everyone Gets Wrong About Stakeholders [blog] Melissa Perri. Designing for consensus of internal people who do not use or buy the products just creates terrible products. Antifragile Software [book] Russ Miles. This book is a collection of patterns that you can apply to build software that thrives on change and the disorder it brings. Streams: a new general purpose data structure in Redis [blog] Salvatore Sanfilippo. One very important use case is time series, but my feeling is that also streaming of messages for other use cases via TREAD is going to be very interesting both as replacement for Pub/Sub applications that need more reliability than fire-and-forget, and for completely new use cases. [DDD Weekly]
- Domain events: simple and reliable solution - Today, I’d like to write about a simple and reliable way to implement domain events. [Enterprise Craftsmanship]