It is has been said that “imitation is the greatest form of flattery” but to borrow an idea is still plagerism. OK, SOA is probably not plagerism but is it really something new?

In the first day’s of programming built into the Assembler language was the BALR instruction which allowed a program to branch and return to a different part of a paragraph or to a completely different program. The sub-routine was invented which set off in motion what seems to be a new fad every 10 years. In the 1960’s Simula 1 was invented followed by Simula 67 that introduced the term object-oriented programming. When I was a COBOL programmer the rage was all about structured programming. The concept was to have a controlling paragraph perform one or more working routines until the work was done. This made following the program as simple as reading the master paragraph which helped eliminate the GOTO verb.

Later the concept of object oriented programming fully hit the market. Everybody needed to get on the bandwagon. Languages were invented, Smalltalk, ADA, Modula-3 and even Java. The C language was extended to form C++. New vocabularies were formed. We now needed to become familiar with the concepts of Classes, Objects, Methods, Inheritance, Encapsulation and let’s not forget Polymorphism. Every new system and marketing campaign needed to have OOP’s in its title. Object oriented databases were created, software packages claimed to be object oriented and even my new coffee maker claimed to be OOP’s capable.

Systems were built that were excruciating slow where the programmer tried to combine objects that did not reside in memory. Operations that should have taken nano seconds if built conventionally now took physical seconds while programs attempted to execute objects that may not resided outside of the program space. Programmers would die in vain trying to debug code that inherited their functionality from a plethora of sub-classes. Clearly, all of this could be avoided and object orientation is not to blame. There is no replacement for sound practical architecture.

Over time the excitement over object orientation began to fade. Programmers used the new languages mainly C++ and Java and object orientation began to transform into a normal tool of the technologist. However, the software manufacturers needed a new fad to stimulate business. A new concept was born and Service Oriented Architecture (SOA) was born. At first I thought this was just another name for Object Oriented programming. I soon found that SOA came with its own set of verbs. The concept of a service needed to be grasped. A new paradigm shift was in the making, it seemed like I would need to go out and buy a new coffee maker, and my object oriented machine was obsolete.
It is said that SOA is not just Architecture but rather a set of policies, practices and framework by which we operate.

I am not sure what is new here. We learned this back in the days of Assembler, Structured Programming reinforced the concept and Object Orientation cemented the theory to all but the truly hard headed.

You do not have flash or javascript support.

Average (1 vote)

Reply