The main difference between batch jobs and real-time jobs is that a real-time job (when configured as a real-time service) is running constantly. It waits for input messages, executes, and returns a result - which can contain many elements. An example might be a validation engine, it would accept many (potentially parallel) input messages and reply (hopefully) in a very short time. It can support a high level of throughput (if designed correctly).
When batch jobs are executed, they start processes to perform transformation and cannot return a complex reply back to the initiator.
Calling both types via the web service are valid and realistic scenarios, a real-time job would be used for fast processing of small input messages and consumable replies, a batch job could be triggered by an enterprise scheduler once a week to export a large volume of data to a 3rd party.
No comments:
Post a Comment