Key benefits of architecting loosely coupled SOA-based solutions

Service-oriented architectures (SOA) experience the most benefits when architects use loose coupling to build their solutions.

The goal of every SOA architect is to develop a highly componentized, largely de-coupled system that makes application lifecycle management (ALM) easier -- from the start of the systems development lifecycle (SDLC) right through to the end. But are loosely coupled SOA-based systems always the answer? And isn't it true that, in some cases, tightly coupled systems aren't such a bad thing?

In this interview with the author of the best-selling Manning publication SOA Patterns, Arnon Rotem-Gal-Oz (@arnonrgo) explains the benefits of loose coupling, why loose coupling is important to service-oriented architectures and, most important, when tighter coupling might actually make sense when developing an application.

Dig Deeper on Software development best practices and processes

App Architecture
Software Quality
Cloud Computing