Hardware and software components that interact when necessary, but remain uncoupled from each other. For example, computers in a network are loosely coupled. When the user's client machine requires ...

One project I worked on a few years back required every interaction with the server to first go through a servlet, a validation interface which then hit a required Business Delegate class, a Session ...

Loose coupling is always a good idea. After all, what's wrong with abstracting away separate layers of concern, creating pluggability points, making your design more flexible, and creating a software ...

A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...

One of the things we talk about here is how service orientation is enabling the rise of the "loosely coupled" business -- an organization that acts as a broker of services, focusing on its core ...

Coupling and cohesion are distinctly different concepts but often confused. Coupling is the degree of dependency between an application’s modules or components, i.e., the strength of the relationships ...

A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...

Loose coupling is one of those suddenly popular great ideas that have actually been around for a long time. With loose coupling come two significant benefits long sought by business and IT managers: ...

Internet transactions, business-to-business systems, peer-to-peer processes, and real-time workflows are too dynamic and too complex to be modeled by traditional sequential-processing methods.