DDD Weekly: Issue #29- Eric Evans: DDD is Not for Perfectionists [blog] Jan Stenberg. “Evans does not recommend working with a model until it’s perfect, as then we will not ship any software. We have to get over the idea that design is something which you invest some extra time in upfront and get paid off in the long run. However, we mustn’t go to the other extreme either, just hacking out something horrible and shipping it.
[DDD Weekly]
Permalink |
From 20 February 2017 to 26 February 2017 |
Last updated on: Mon, 7 Jun 2021 09:10:50 GMT
DDD Weekly: Issue #28- Domain Events vs. Integration Events in Domain-Driven Design and microservices architectures [blog] Cesar de la Torre. “This blog post is about comparing several approaches of Domain Events vs. Integration Events patterns already published by the community” Why Every Single Element of SOLID is Wrong! [slides] Dan North. “Write simple code!” A study on Versioning in Event Sourcing [request from community] Michiel Overeem. “We are searching for developers/architects willing to cooperate in a study on versioning in event sourcing.
[DDD Weekly]
Permalink |
From 06 February 2017 to 12 February 2017 |
Last updated on: Mon, 7 Jun 2021 09:10:50 GMT
DDD Weekly: Issue #27- Building Event-driven Microservices Using CQRS and Serverless [blog] Kenny Bastani. “This blog series will introduce you to building event-driven microservices as cloud-native applications.” From dependency injection to dependency rejection [blog] Mark Seemann. “Several years ago, I wrote a book called Dependency Injection in .NET, which was published in 2011. The book contains examples in C#, but since then I’ve increasingly become interested in functional programming to the extend that I now consider F# my primary language.
[DDD Weekly]
REST API response codes: 400 vs 500- Today, I’d like to talk about the (sometimes subtle) difference between 4xx and 5xx response codes when programming a RESTful API. I’ll try to show when to return what code (400 or 500) and introduce a simple way to implement this logic on the server side.
[Enterprise Craftsmanship]
Permalink |
From 30 January 2017 to 05 February 2017 |
Last updated on: Mon, 7 Jun 2021 09:11:14 GMT
DDD Weekly: Issue #26- Bus or Queue [blog] Steve Smith. “A common question I encounter is, ‘what is the difference between a message bus (or service bus) and a message queue?’” Donkey Code [blog] Einar Høst. “The point of this example is that it takes very little for software development to get crippled by complexity without precise language. You need words for the things you want to talk about, both in design discussions and in code.
[DDD Weekly]
Permalink |
From 23 January 2017 to 29 January 2017 |
Last updated on: Mon, 7 Jun 2021 09:10:50 GMT
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]
Permalink |
From 16 January 2017 to 22 January 2017 |
Last updated on: Mon, 7 Jun 2021 09:11:14 GMT