• Post Reply 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
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Single vs Mutiple Web Services

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I am in the process of creating a Webservice for my application which needs to provide two operations/functions to handle different request.
I am having two options in my mind.
1)First one is creating a single webservice with 2 operations/functions like below
Ex: TestService
a)AddNum
b)Mutilply
2)second one is creating a web service for each operations/functions like below
Ex:AddNumService
MutilplyService

I am not sure which is one the right option.

Please share your thoughts on this.

Saravanan




 
Ranch Hand
Posts: 171
Hibernate Spring Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The base behind this decision should be exactly same as the base of writing classes. Similar operations in one service. In the example you mentioned, you can have one MathService or CalculationService & put related operations into it. but if there is something else ..lets take login/logout for example, then there should be another service for login/logout.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic