Ok, so why isn't a standard webservice cgi/fascgi/mod_php, etc not
sufficient for that kind of parallelism?  With multiple users making
requests, they will all happen in parallel. 

On Mon, Apr 28, 2014 at 07:53:37PM +0530, Deepak Sharma wrote:
> We need parallelism here.
> As lot of users may be using the service at the same time.It may be for
> different file or the same file.
> 
> Thanks
> Deepak
> 
> 
> On Mon, Apr 28, 2014 at 7:41 PM, Marc Vaillant <[email protected]> 
> wrote:
> 
>     I think it's important to know whether or not some form of parallelism
>     (other than throughput) is required, otherwise a standard webservice
>     seems sufficient for this use case.
> 
>     On Mon, Apr 28, 2014 at 07:46:35AM -0400, Andrew Perepelytsya wrote:
>     > You can build request response type topologies via DRPC. However, unless
>     we're
>     > talking about processing numerous pdfs at once - bad fit, IMO.
>     >
>     > If there is parallelism required you might be better off with a custom
>     yarn app
>     > - looks like YAYA makes it tolerable top write.
>     >
>     > Andrew
>     >
>     > On Apr 28, 2014 2:41 AM, "Deepak Sharma" <[email protected]> wrote:
>     >
>     >     Hi All,
>     >     Just wanted to check if this can be valid storm use case.
>     >     I want to write 1 simple storm topology which can read pdf file ,
>     process
>     >     it , make some changes like convert it to doc and save the new file.
>     >     I know this can be easily done in batch mode using hadoop.But we 
> want
>     to do
>     >     it in real time ,i.e. when the user demands it.
>     >     We already do it using some java api but it takes lot of time in all
>     >     conversions.
>     >     Can this be achieved in Storm?If yes , Is there any pointer to any
>     examples
>     >     similar to this use case?
>     >
>     >
>     >     --
>     >     Thanks
>     >     Deepak
>     >     www.bigdatabig.com
>     >
>     >
>     >
>     > CONFIDENTIALITY NOTICE
>     > NOTICE: This message is intended for the use of the individual or entity
>     to
>     > which it is addressed and may contain information that is confidential,
>     > privileged and exempt from disclosure under applicable law. If the 
> reader
>     of
>     > this message is not the intended recipient, you are hereby notified that
>     any
>     > printing, copying, dissemination, distribution, disclosure or forwarding
>     of
>     > this communication is strictly prohibited. If you have received this
>     > communication in error, please contact the sender immediately and delete
>     it
>     > from your system. Thank You.
> 
> 
> 
> 
> --
> Thanks
> Deepak
> www.bigdatabig.com
> www.keosha.net

Reply via email to