Ideal way/architecture to deliver large data over Web Services
Posted
by zengr
on Stack Overflow
See other posts from Stack Overflow
or by zengr
Published on 2010-04-17T05:05:43Z
Indexed on
2010/04/17
5:23 UTC
Read the original article
Hit count: 183
We are trying to design 6 web services, which will serve another client component. The client component requires data from the web service we are implementing.
Now, the problem is, there is not 1 WS we are implementing, there is one WS which the client component hits, this initiates a series (5 more) of WSs which gather data from their respective data stores and finally provide the data back to the original WS, which then delivers the data back to the client component.
So, if the requested data becomes huge, then, this will be a serious problem for our internal communication channel.
So, what do you guys suggest? What can be done to avoid overloading of the communication channel between the internal WS and at the same time, also delivering the data to the client component.
© Stack Overflow or respective owner