• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Frits Walraven
Bartenders:
  • Carey Brown
  • salvin francis
  • Claude Moore

Service Calls  RSS feed

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Service A sitting on JBOSS want to talk to Service B on Tomcat . Here  Service B is supposed to  perform multiple operations say 4(Create a Directory,Write to a file(Few KBs) and save it to directory,Update a DB Table and send an email).

is it optimum to refactor service B in 4 small services  and trigger those 4 from Jboss ? or i should have only one service only doing 4 stuffs in one shot ?  

 
Bartender
Posts: 1120
38
IBM DB2 Java Netbeans IDE Spring
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In the sceanrio you described I would not refactor Service B. Personally I tend to keep REST services more coarse grained as possible,  preferably as a composition of more service classes I write as if they were library classes. I can't see the point of calling 4 different endpoints, to perform relatively simple operations like the ones you are talking about.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!