Dimensions of coupling in middleware

Abstract

AbstractIt is well accepted that different types of distributed architectures require different degrees of coupling. For example, in client‐server and three‐tier architectures, application components are generally tightly coupled, both with one another and with the underlying middleware. Meanwhile, in off‐line transaction processing, grid computing and mobile applications, the degree of coupling between application components and with the underlying middleware needs to be minimized. Terms such as ‘synchronous’, ‘asynchronous’, ‘blocking’, ‘non‐blocking’, ‘directed’, and ‘non‐directed’ are often used to refer to the degree of coupling required by an architecture or provided by a middleware. However, these terms are used with various connotations. Although various informal definitions have been provided, there is a lack of an overarching formal framework to unambiguously communicate architectural requirements with respect to (de‐)coupling. This article addresses this gap by: (i) formally defining three dimensions of (de‐)coupling; (ii) relating these dimensions to existing middleware; and (iii) proposing notational elements to represent various coupling integration patterns. This article also discusses a prototype that demonstrates the feasibility of its implementation. Copyright © 2009 John Wiley & Sons, Ltd.