Saturday, August 16, 2014

"SOA Developer" - Really?

I have been looking at some of the developer related job ads and many a time I come across a job with title "SOA Developer". I cannot understand this really. Within the description it specifies a particular tool/technologies such as Oracle SOA Suite.

As I understand, SOA is an architecture not a language or framework or anything much technical. If the employer mean "SOA architect" by the title "SOA developer", I do not have problem with that because architecture in SOA should be "developed" by an architect.

So whats the real position should sound like. May be "Service developer" but that will be too abstract. So, it boils down to "orthodox" - BPEL developer or Java developer. I guess, because of so much hype about SOA, it has turned into business of selling product in the name of "architecture" and nothing is achieved by organization except for pain in terms of money and effort to look for tool specialists, pay hefty licence and build (Mostly un-scalable) infrastructure in order to run the tool.

If there is any title begins with SOA, in my view, the next word should be either "Administrator" or "Architect" just to be clear. Once the architecture is done, then a tool should be selected to implement the services or to wrap the legacy application with service layers. Then and only then there will be a need for a developer/coder to build the service. But most of the time, organization has already invested in one technology, say dot net or Java, so it does not harm to have "Java developer" or ".NET developer" from the inception of a SOA project but the job title should state exactly that and not "SOA developer".

No comments:

Welcome to my blogs

The contents here are my independent point of view. They reflect my thoughts, experience in my professional and social life.

Search This Blog