Re: What databases have taught me
From: Robert Martin <unclebob_at_objectmentor.com>
Date: Fri, 30 Jun 2006 19:52:01 -0500
Message-ID: <2006063019520150073-unclebob_at_objectmentorcom>
> It's a matter of perspective. From the perspective of web services
> people, for example, all of your examples of decoupling are in fact
> examples of tight coupling, through dependencies on language bindings
> and platform. From the web services perspective, decoupling is
> achieved through the standardization of the format of documents.
Date: Fri, 30 Jun 2006 19:52:01 -0500
Message-ID: <2006063019520150073-unclebob_at_objectmentorcom>
On 2006-06-28 07:41:05 -0500, "Daniel Parker" <danielaparker_at_gmail.com> said:
>> >> It is not hiearchy that drives OO, it is dependency management. It is >> the decoupling of callers from callees through the mechanisms of >> dynamic polymorhism that is the driving force behind OO design. >>
> It's a matter of perspective. From the perspective of web services
> people, for example, all of your examples of decoupling are in fact
> examples of tight coupling, through dependencies on language bindings
> and platform. From the web services perspective, decoupling is
> achieved through the standardization of the format of documents.
Granted. Though this is not new, nor related strictly to web services. Any set of services that communicate through a standard message format provides a level of decoupling.
OO provides decoupling at a smaller granule than services like these. OO provides for coupling *within* the code of the services. OO provides decoupling at the *line-of-code* level.
-- Robert C. Martin (Uncle Bob) | email: unclebob_at_objectmentor.com Object Mentor Inc. | blog: www.butunclebob.com The Agile Transition Experts | web: www.objectmentor.com 800-338-6716 |Received on Sat Jul 01 2006 - 02:52:01 CEST