Distributed applications and OOD

From: Fredrik Bertilsson (fredrik_bertilsson_at_passagen.se)
Date: 09/11/04 

Date: 10 Sep 2004 21:45:39 -0700

For developing distributed applications, using EJB or Web Services,
following pattern is very common: Data is transfered between the
client and server using value-objects which purpose is to hold data
and doesn't implement any logic at all. On the server-side, client
requests are handled by facade objects that are stateless, which means
that they have no member variables. Behind the facade layer there use
to be a business logic layer or data access layer that are also
stateless. All layers on the server-side use to operate on the
value-objects.

>From my point of view this does not look like a object oriented
design. You have pure data objects and pure functional objects. But
still it is the only working design for distributed applications.
Every attempt to have objects containing both data and logic, will
have drawbacks. For example, if you use this kind of objects on the
server-side, you still have to write data transfer objects, which will
carry almost the same data as the "real" object, and you will have
duplication in your code.

What do you guys think of this?
* This design is a bad design.
* Or, this is still a good OO design.
* Or, OO design is not suitable in distributed applications.
* Or???

/Fredrik

Relevant Pages

  • Re: Distributed applications and OOD
    ... > For developing distributed applications, using EJB or Web Services, ... Behind the facade layer there use ... All layers on the server-side use to operate on the ... > still it is the only working design for distributed applications. ...
    (comp.object)
  • Re: Distributed applications and OOD
    ... > client and server using value-objects which purpose is to hold data ... Behind the facade layer there use ... All layers on the server-side use to operate on the ... > still it is the only working design for distributed applications. ...
    (comp.object)
  • Re: Distributed applications and OOD
    ... >requests are handled by facade objects that are stateless, ... All layers on the server-side use to operate on the ... >still it is the only working design for distributed applications. ... Don't confuse the design of the protocol with the design of the ...
    (comp.object)
  • JSP/Struts Progammer position - Wireless Software
    ... The Java Developer is responsible for designing and developing custom, ... server-side Java engines and a JSP portal. ... * Design & develop web-based administration portal which utilizes JSP, ...
    (comp.lang.java.programmer)