Nowadays everybody is talking about the Real-Time-Enterprise and sometimes it looks like that there is nothing else that counts anymore. Everything has to be done simultaneously or at least immediately. In this urgent world batch-thinking is becoming more and more notorious – even after work when you are with friends. You need an opinion and you need it immediately – no matter how stupid or awkward it comes along.
You know these people who always mix up “urgency” and “importance”? They simply jar on the nerves because they don’t want to see that there are things which are urgent but not important and vice versa. They bug because sometimes it is important that tasks are done precisely and without failure.
That is where good old Job Scheduling maintains its ground. Of course it has changed over time – so much that a recent Gartner Publication from April 2008 talks about Job Scheduling 2.0 when it comes to the integration issues we have to face nowadays. Batch-Jobs are no longer located on islands, and their results have to be distributed to other applications and systems inside and outside the enterprise. But it also points out that Real-Time is not everything: “Most application integration vendors focus on real-time or near-real-time application integration. For example, a CRM transaction needs a prompt response from a back-end ERP package. However, 70% of the required integration is batch. This is where batch data is not processed in real time or online while the user is waiting.”
Think of yourself as a tourist. Booking a flight online you will need some data immediately, others not. This defers to a world beside the Real-Time-World – existing and prosperating – in which being offline is not just giving you back your own rhythm but sometimes makes you even more effective. Remember this.