Design Practices

Integration Gateway for External Systems

An Integration Gateway isolates your system from external changes and failures while standardizing communication. This article explores a Code Design approach using Contract-First Design, Pluggable Applications, and Clean Architecture for reliable and maintainable software integration.

Detailed Technical Design: Bridging Architecture and Code for Predictable Delivery

Detailed Technical Design bridges architecture and code. By defining requirements, contracts, and code design upfront, teams gain predictability, reduce rework, and build consistent structure, leading to efficient, maintainable software delivery.

Decide between In-Process or Inter-Process Communication at Deploy Time - Part 3

This is the last post from the series on how we could implement a design that allows to decide only at deploy time how two services communicate: in process if they are deployed on the same server or inter-process if they are on different machines. The first post shows where

Decide between In-Process or Inter-Process Communication at Deploy Time - Part 2

This post continues the previous by giving an example on how we could implement a design that allows to decide only at deploy time how services communicate: in process if they are deployed on the same server or inter-process if they are on different machines. If you haven't

Decide between In-Process or Inter-Process Communication at Deploy Time

After a long vacation in October last year, followed by some intensive work at MIRA and InfiniSwiss, now I can make some time to share some more design ideas that I have implemented along the years. I thought to resume blogging with showing how we could design for something which

AppBoot Library

AppBoot is a generic .NET application bootstrapper, we at iQuarc, have put on GitHub a while ago. It started few years back when we were about to begin developing a large enterprise application. Back then, we wanted to use the Unity Container for dependency injection, but we liked the way

Crosscutting Concerns

The Crosscutting Concerns are the areas in which high-impact mistakes are most often made when designing an application. There are common causes that lead to this and there are common practices that can help to avoid such mistakes. In this post I will talk about the way I usually address

DRY vs Coupling

While reviewing my previous post another great discussion, which may arise from paying attention to your references, came to my mind: Don’t Repeat Yourself (DRY) vs Coupling. Each time you add a new reference it means that you want to call the code from the other assembly, therefore you

Using ReSharper for Assembly References Diagrams

A few posts back I talked about how we can use the assembly references to enforce consistency and separation of concerns (here and here are the old posts). I argue there that if we derive from the architecture the assemblies of our application, the kind of code (responsibility) each one

The Code Design Training

It was few months ago more than a year ago (22nd of February 2013 in my Trello card, Ideas column), when I came up with the thought of developing a training about how to write good code. At that time I was doing a lot of thinking about how to