A facade is meant to simplify the interface to an underlying object (or set of objects), or to reduce dependencies between the underlying objects and the client of the facade. So in that sense, a Service Layer object may often act as a facade. However, Service Layer is also a pattern in its own right and usually has logic or transaction handling that would go beyond the usual definition of a facade. So I would say that while the two are similar in some ways, a Service Layer is specifically meant to encapsulate the domain model and provide functionality that spans multiple domain objects (usually things like transactions, concurrency, caching, and directing calls to multiple different domain objects). Facades, on the other hand, can exist anywhere that needs a simplified interface to something. Hopefully that helps make the distinction.
On Nov 5, 2007 6:32 PM, AJ Mercer <[EMAIL PROTECTED]> wrote: > So in Doug,s Wife, Man, remote controls, TV & DVD story > He states the man is the Service Layer Object. > Are the remotes a facade? > > > Service Layers know how to manipulate objects > Facades hide complex processes > > Is this getting close?? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:292717 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
