[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: APIs, messaging
- From: David Brownell <email@example.com>
- To: "Simon St.Laurent" <firstname.lastname@example.org>, email@example.com
- Date: Wed, 23 May 2001 09:04:43 -0700
> Does that seem like a reasonable breakdown of the situation?
Sure. In the context of distributed systems, I usually call the two
perspectives "tight coupling" and "loose coupling". Most systems
have elements of each.
Bind tightly to anything (API, class/data structure, ...) and you've
developed a system that needs to react to lots of changes -- fragile,
all components have to change in lockstep. As Walter implied,
viable only within artificially constrained environments; basically,
where centralized control works.
But if you have a carefully specified framework that works with a
more flexible notion of "type" ... that's the sweet spot, where the
components (organizations ...) can evolve at their own rates. A
better match, on the whole, for the Real World.