Applying Domain-Driven Design and Patterns: With Examples in C# and .NET

Chapter 1. Values to Value: Or Embarrassing Ramblings When Self-Reflecting on the Last Few Years This chapter's intention is to set the scene. I will do that by looking back in time over the last few years regarding how I have thought about ...

Overall Values In the past, I was very good at planning ahead. I often added functionality, structures, and mechanisms to my projects proactively. That part usually turned out pretty well, but I often forgot about the artifacts added on that never...

Architecture Styles to Value Architects and developers must make design decisions based on the requirements of the project. I haven't collected an exhaustive list of values regarding architecture styles here, but I have decided on a few main thing...

Process Ingredients to Value I'm not much of a process guy, but I still would like to add a couple of thoughts. Before I get started, what do I mean by "process"? It's the methodology for moving forward in projects: What should be done, ...

Continuous Integration I'm sure you all recognize how big a showstopper manual integration on a monthly basis, for example, can beeven if your team just consists of two developers on a project. The problem increases exponentially when you add mo...

Don't Forget About Operations Not too long ago, I was talking to a team at a large Swedish company. I talked, for example, about the Valhalla framework and how it looked at that particular point in time. They asked me how we had dealt with operat...

Summary We ended the chapter with a few words about operational aspects. We won't discuss that much more in this book. Instead, the focus will be about the core of the applications, the core business value. The discussion in this chapter about wh...