Why is this relevant for SOA? Well here is an example of an incredibly efficient batch system which is based around time synchronisation and which therefore is able to move large numbers of people successfully around. A "real time" process based solution would be the car. Start at A, do lots of steps, arrive at B. But with the railway system, which is much more event based, is able to achieve the same end game (indeed there are parts of Switzerland where cars cannot reach) but do so in a way that reduces stress and increases efficiency.
So when you are looking at replacing those old Batch processes which look so inefficient, ask yourself whether they are batch processes because that is all that could be done, or whether you have a Swiss Railway implementation that you are about to replace with a butt ugly SUV.
Technorati Tags: SOA, Service Architecture
2 comments:
Your conception of batch is very different from what an IBM Cobol developer thinks of as batch. Trains moving from point A to B are online, real time activities.
How is that a batch process?
The people on the train are the batch process. So instead of a real-time single person (event) based approaches you are shifting people in bulk from one process to another.
Basically its the difference from doing car to car transfer and using trains.
Post a Comment