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
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
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
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
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
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)
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
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
Founder and Partner
Partner
Recent posts
- Why Programmers Should Challenge the Stakeholders
- Migrate to Ghost 1.x on Azure
- Decide between In-Process or Inter-Process Communication at Deploy Time - Part 3
- Decide between In-Process or Inter-Process Communication at Deploy Time - Part 2
- Decide between In-Process or Inter-Process Communication at Deploy Time