01-23-06 11:02 PM
Hello gavkel,
Yes and no.
The parallel shape does not process in parallel per se, if it finds itself
waiting for a message or something similar, it will process the other branch
while its waiting. So, if for example you call a web service and have some
business rules calculations to make (unrelated to the web service response)
then you can make those calculations in a seperate parallel branch.
When the web service request is sent, the other branch processes the rules
while the web service side waits for the response.
In this example you would achieve better performance.
"The parallel shape is for receiving multiple messages when you don't know
what order they come in." is in fact true, but not the only case where you
could take advanatge of it.
Another description might read "One way to leverage the parallel shape is
to process unrelated messages when you expect to be waiting for a process
to complete"
Hope this helps,
BA
http://biztalkia.blogspot.com/
> Hello there
>
> Would appreciate a bit of advice on the Parallel shape and parallel
> jobs running though an Orchestration.
>
> We have a Orchestration that calls a number of components and web
> services - it was initially designed to use a parallel shape within a
> long running scope. I since read this may not be the best approach and
> just calling things sequentially would prove faster and more reliable.
>
> "The parallel shape is for receiving multiple messages when you don't
> know what order they come in."
>
> Is this true? Any feedback would be appreciated.
>
> Thanks
> Gav
[ Post a follow-up to this message ]
| 
