Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

Service Layer design

 
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Report post to moderator
Hi,
I am trying to design a service layer. Service layer interacts with many clients via remoting but all the clients related to same business group.
My question is how do I design my service for loose coupling


say client 1 needs

PersonResponseDTO getPersonDetails(PersonDTO)

say client 2 needs
PersonResponseDTO getPersonWithAllHisPets(PersionDTO)


PetResponseDTO getPetsWithNoOwners(PetDTO)


My concern here is, I start having DTO's like this I will end up creating lot of DTO's.
I am afraid this is tight coupling.
we can exchange data with xml but I do not want parsing overhead because these application purely internal.
How best I can take input from client and give response back.
Since each client need different level of details, do you guys know how best we can achive this?
 
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Report post to moderator
Please do not duplicate post.

Closing this thread as it is a dup of

https://coderanch.com/t/464390/Java-General/Service-Layer-design

Thanks

Mark
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic