Week 3, year 2017
- User Interface - This post will conclude our story of a Vertical Slice of an application build to help First Pop Coffee Company be more successful with its Roast Planning. We are far from finished, as I know that the pain in actually implementing these architectural principles is stronger than I can describe with a single Bounded Context. [Nick Chamberlain on Nick Chamberlain]
- The Read Model Facade - We’ve covered how we get data into our Read Model via our special Read Model Projections that use Entity Framework to insert View Model objects into a read-optimized SQL Server table. The table stores View Model objects in it, reducing the impedence mismatch we would run into if we didn’t have a separate Read Model. But how do we actually use the Read Model SQL Server? [Nick Chamberlain on Nick Chamberlain]
- DDD Weekly: Issue #25 - 10 Prolems in Software Projects [blog] Joy Clark. “As an introduction to the reason why to use DDD, the author listed out 10 problems that are commonly found in software projects (which also should be able to be solved using DDD). I agreed with a lot of them. And I thought to myself… That would make a good sketchnote! So I made one. I’m looking forward to the rest of the book. [DDD Weekly]
- How long should a single method be? - This topic might seem trivial, especially if you look at all other articles that have beaten it to death already. But I would still like to make a couple of important points here. So, how long should a single method be? [Enterprise Craftsmanship]