Description
Some components are introduced, in order to make a relatively fast adaption such that the established environment is working, although this temporary solution does not represent the desired or intended solution. This is the very common view of debt being taken.
Context
Inspired by: “Temporary Field”
Oftentimes, those adaptions are made “on the fly”, without a full model being designed.
Cause
In order to keep the architecture working, adjustments have to be made shortly. Those adjustments are no optimal solutions resulting in cluttered abstractions and messed up architecture.
Solution
Increase the awareness of those faults and refactor such that a supposed ideal solution is pursued.
Example
The EA is currently relying on a System A. In the long run a System C should be used to realize the roadmap, but as the integration of that system is delayed a temporary solution B has to be integrated, because data from System A is still used. Such actions increase the dependency and hinder the intended development.
Tags
soa, microservices, business, application, technology