For those of us old enough to have worked in the mainframe days of MVS, much of the buzz of SOA seems awfully familiar.
See in the olden days, there was a mainframe which contained all the data and programs. It provide “services”, such as data storage services, memory services, printing services, display services, communication services, backup services ….
MVS was the grandfather of all SOA. The divorcing from the mainframe and movement to client server and eventually internet architectures caused all the built in services that came with the mainframe to go away. Strike the sheppard, scatter the flock, so to say.
In the world of client server SOA or replication of the MVS model was nearly impossible. Thus when we moved to toward a more centralized internet (thin client) model over the past few years, the yearning for the past (even for those who it was not part of their past) crept in. Thus the birth of SOA.
Do not get me wrong, I am not saying today’s SOA is as archaic as MVS (remember, there is a IBM 360 in the Smithsonian), but let’s learn from some of the good points of the grandfather of SOA.
- Services were predictable
- Services were tracked and charged
- Services were scalable (if you had the money!)
- Services were application driven
- Services were standard from company to company (MVS at your company was the same as MVS at mine)
Some pretty good things for today’s SOA to take as principals, right?