That’s it, you heard me correctly. The Service Oriented Architecture (SOA) really is a thing that transforms gibberish into simplicity.
If you look more closely, even the term itself would sound gibberish to the untrained ear.
This is a computer program that was developed by a Business Process Expert, a new breed of computer experts that specializes both in business and information technology (IT).
Now why did I say gibberish in the first place? Simple, it is very hard for an ordinary person to understand.
It would even look like alien writing to some.
But it is still working, doesn’t it? So backing up some, can you understand it?
Of course not, and now with the current pace of today’s business, which I might add changes everyday and have already found a likely ally, called the Internet, there is an urgent need to combine business and IT.
So now, imagine yourself as having a business that has an online website.
Sometime in the future, you are then faced with a task of updating your online website to be on line with your business.
But instead of seeing a simplistic program, you see program full of writings of would-be programs that you don’t even understand.
So you hire a computer programmer to do it for you, but then he comes back to you saying, "Sir, to be able to do these updates, I’ll need to change your programming code."
Added fees and more hassles will surely come to you because of this.
BUt with the SOA, there is a sure-fire chance that you will no longer have to change your programming code.
You see, what SOA really does is string all the programming codes together through Orchestration, which will then form ad-hoc applications from your existing programming code.
While applying SOA does help in the sensible and controlled approach to a project, it
should be noted that the tools are only as good as the behaviour and willingness of the
people involved in the SOA development. Governance in SOA assures that there is
always a systematic, dynamic, and disciplined planning and implementation of the
SOA. Avoiding a poorly constructed and poorly executed SOA is the main objective
of governance in SOA.
SOA and governance go hand in hand when it comes to handling complex application
interconnection. Since SOA can be approached either as a whole (enterprise level), a
part of a whole (department, regional, or division level), or a single part of a part (one
application of a department), if there is no governance, the SOA lifecycle will be
challenged by human and technical difficulties. SOA governance is needed in order
for the process to be structured and disciplined. Without a properly disciplined
planning and decision making control, a program may be started but will just turn out
to be another confusing and complex program added to the system.
There are challenges like who makes the decisions, what SOA is to be prioritized and
worth considering, who will manage and how effective is it and what do we mean by
“effective”? This is the basic concept of governance in SOA: planning for the overall
scope, identifying compliances, defining the processes, and putting everything into
action. And the only way to have governance in SOA is to treat it as a business
investment which everyone should be committed to be involved in.