wood burning stoves 2.0*
The moose likes Web Services and the fly likes Scalability in web services Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Scalability in web services" Watch "Scalability in web services" New topic
Author

Scalability in web services

Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

How do I make my web services application scalable? Any tips would be great.


Groovy
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Tip #1: Keep your web service stateless

Tip #2: Make your web service asynchronous


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Jim Bracks
Ranch Hand

Joined: May 04, 2004
Posts: 42
How do I make my web services application scalable? Any tips would be great.



By choosing the right product for exampleSystinet product performs faster than those from Apache Axis and Sun jwsdp.Scalability may vary based on configuration.Run benchmarks that simulate the requirments of your production applications.


Jim.
[ June 15, 2004: Message edited by: Jim Bracks ]
J. Acc.
author
Ranch Hand

Joined: Jun 14, 2004
Posts: 33
Lasse�s tips are great. I�d add a few more:
Tip #3: Design your services with appropriate granularity.
Tip #4: Design your services with clear functional boundaries.

These design characteristics will help you build an SOA consisting of distinct and highly composable services. This will allow you to use specialized services with targeted functionality (and less processing overhead), but it will also let you aggregate your services for larger tasks, when required.

Then, of course, there are the real world considerations. Your SOA�s underlying infrastructure will need to support the distribution pattern you�ve chosen for your Web services, and all of the middleware that may be processing the message flows behind the scenes. Also, there are often security considerations that can affect service design and performance, as well as an SOAs infrastructure requirements.
H Rice
Greenhorn

Joined: Jun 15, 2004
Posts: 5
Originally posted by Lasse Koskela:
Tip #1: Keep your web service stateless

Good points. On the stateless point, there are two types of implementations (jaxrpc or stateless ejb). you probably need to weigh on this as well.
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

Tip #2: Make your web service asynchronous

Asynchronus? Does it mean document style messaging.
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Originally posted by Pradeep Bhat:
Asynchronus? Does it mean document style messaging.

Not necessarily. What I meant with asynchronous was that the service replies immediately with an acknowledgement and continues processing the actual service request while the client is waiting or doing something else. When the service request has been processed, the service sends the results to the client with a new web service request.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Scalability in web services