Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Why Do We Keep Building Tightly Coupled Software?

DZone's Guide to

Why Do We Keep Building Tightly Coupled Software?

Free Resource

Modernize your application architectures with microservices and APIs with best practices from this free virtual summit series. Brought to you in partnership with CA Technologies.

A good friend of mine, Kevin Israel, said on twitter today:

"how freakin long are *we* gonna keep building tightly coupled software that needs to constantly evolve!?"

At first I wanted to say "until programmers stop sucking so much", but unfortunately, there is often much more to the picture than the usual "you're surrounded by idiots" response. Many of us do continue to build tightly coupled software, and we do it for a variety of reasons. Some of us just don't know any better, we've never been exposed to or experienced what exactly people mean by "loosely coupled" software. Others see creating loosely coupled software as another layer of complexity that they just don't need inside of their applications. And yet others, have seen and experienced it, but still don't understand how to implement it effectively. Unfortunately, at this point I think that majority of developers fall into the first camp, they just don't know what it means to build "loosely coupled" software.

Read the rest of this post at CodeThinked.com

The Integration Zone is proudly sponsored by CA Technologies. Learn from expert microservices and API presentations at the Modernizing Application Architectures Virtual Summit Series.

Topics:

Published at DZone with permission of Justin Etheredge. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}