Hi,
We are planning to use “Remote Invoke” Calls to access flow services from one IS Server to another. We need the calls to be synchronous
Broker based communication is out of the question , as is webservices based.
Any known issues with Remote invokes or performance concerns,
technically it is the same as invoking another flow within the same server. should be robust enough.
Want to know the community opinion.
Regards,
Austin.
It’s pretty robust and not much of performance issues noticed in this approach… atleast i haven’t. let’s see if someone else has some other ideas.
You might consider an HTTP-based interaction instead of remote invoke. This gives some flexibility to move the called service to some other implementation without needing to change the caller. But that may not be important.
reamon,
I did consider http post, but one of my requirement is to get a synchronous reply back.
I believe http does not support sync calls.
Definitely Open to new approaches ,so that we can compare the pros and cons.
WebService
pro: standard based
cons: additional processing overhead, addtional objects required
Remote
pro: easy calls, robust and fast-In the absence of data to disprove,
cons: proprietary, but then, as are flow services
HTTP post is synchronous. You will get an immediate response.
I think the remote invoke will send the whole pipeline through to the remote server and bring back the whole pipeline. If you have unwanted big pipeline object, that will waste system resource on both servers, also the network traffic. So, clean you pipeline before the call and at the end of the remote service.
correct me if i’m wrong