Decide between In-Process or Inter-Processes Communication at Deploy Time
One of the challenges of designing distributed systems is to decide which of the services that compose the application are loaded in the same process and communicate directly and which should be deployed on different boxes and use inter-process communication. Sometimes, we cannot anticipate this at all and we’d want the flexibility to change it based on usage metrics collected while the system is running in production.
In this session we will learn, from real life projects experience, how we can achieve the flexibility of deciding only at deploy time, without changing the code, on which of our services communicate in same process and which use inter-process communication.
We will achieve this using the iQuarc.AppBoot library, which is an abstraction over a Dependency Injection Container and provides support for modular applications. During the session we will start coding an infrastructure for such an application, inspired from real life projects which, later on, could be evolved to accommodate the specific needs of a real application. We will address the On-Premises scenario for .NET applications and, at the same time, the code we’re going to write can be adapted for the cloud scenario.
Who is it for?