• EventStorming's Coincidence with Business Process Improvement - The purpose and implementation of EventStorming doesn’t only exist inside of Domain-Driven Design. Although the name “EventStorming” does tie itself to DDD, it has foundations in process improvement that have nothing to do with DDD and these are not new. Parallels with business process improvement and LEAN One technique that I’ve personally seen is business process improvement exercises used in Manufacturing to discover bottlenecks. Here, the same issue applies - Domain Experts aren’t fully aware of the bottlenecks outside of their processes. They live in a silo. While one process works well in their division - say the Accounting Department, the interaction with their division that includes this process is potentially a bottleneck for an outside division, like Sales. [Nick Chamberlain on Nick Chamberlain]
• DDD Weekly: Issue #43 - Evolutionary Pressures Forcing Software Architects to Adapt [blog] Nick Tune. To remain effective, you must learn to co-design and coevolve organisational and technical boundaries. You’re not a software architect anymore, you are a sociotechnical systems architect. Power of the Log:LSM & Append Only Data Structures [video] Ben Stopford. Ben Stopford talks about the beauty of sequential access and append only data structures, in the context of a little known paper entitled “Log Structured Merge Trees”. [DDD Weekly]

Permalink | From 25 September 2017 to 01 October 2017 | Last updated on: Mon, 7 Jun 2021 09:10:50 GMT

• Let's ship something together... - If you need a hand with your project, I am available to provide some assistance with various parts of your .NET projects. [Nick Chamberlain on Nick Chamberlain]
• Optimistic locking and automatic retry - In this post, I’m answering a reader’s question about how to combine an optimistic locking and automatic retry. [Enterprise Craftsmanship]

Permalink | From 18 September 2017 to 24 September 2017 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

• How do We Write Factories for Event Sourced Aggregates? - Take the following use case: I have an Employee aggregate I want to create a new Employee I wrote Employee.Create(...) …but Aggregates don’t create themselves (Don’t Create Aggregate Roots), especially when it’s a clear use case where someone like an Admin is responsible for creating new Employees. We’re suppose to create a factory for situations like this. This way, the factory can ensure invariants are enforced on the creation of the Aggregate, just like the Aggregate enforces invariants on any other state changes. But, when I created a static factory Employee.Create(...) and intend for Employee to be an Event Sourced Aggregate, when/where/how do I send my EmployeeCreated event so that it gets saved to the Event Store? [Nick Chamberlain on Nick Chamberlain]
• Using Event Sourcing in a Legacy Environment - Have you ever been met with deaf ears when you tell your team there are benefits to thinking about architecture differently? What about when you bring up buzzwords like “Event Sourcing” or “Domain-Driven…”? I have, which is why I write about it… [Nick Chamberlain on Nick Chamberlain]
• Event Sourcing and CQRS sample code - We just published some new sample code to our public Github account. It includes samples for Event Sourcing with Java and using our APIs with Golang. Please check it out! [Serialized development blog]
• DDD Weekly: Issue #42 - Why Software Hasn’t Worked for You [blog] Vaughn Vernon. This article is meant, not primarily for the software developer or project manager, but for the strategically qualified and motivated business professional. Its goal is to challenge the status quo of business software development and introduce an approach that may appear as novel in most enterprises. This approach focuses on delivering critically distinguishing solutions that are intended to propel business toward greater commercial success. [DDD Weekly]

Permalink | From 11 September 2017 to 17 September 2017 | Last updated on: Mon, 7 Jun 2021 09:10:50 GMT