Even if the concept of a Service Orientated Architecture (SOA) looks revolutionary compared with the antique appearance of a batch mode culture, it’s not drawing a line under background processing. The remaining dependency is illustrated by the fact, that over 50% of all applications still perform their processing in a background manner.
This is possible through the existence of Workload Automation tools bridging between SOA and legacy applications and ensuring that the user/client gets the needed information in time. Of course, batch is not real-time. But the automation engine that supports SOA processing initiation in background is establishing the required connection to process jobs under the SOA-umbrella.
You mean, “in-time” is a woolly concept? No way! Look at the user/client. He defines it – and not just in this cartoon.