LOGIN | REGISTER NOW | SUBSCRIBE
 
print Printable version 
Most Read Latest News Blog Resources
CouchDB brings peer-based data replication
This NoSQL database is now production ready for developers who want to spread data out wit...
Experts: UML is active, but the buzz is lost
Since widespread acceptance, there is little enthusiasm around the language even ahead of ...
Compuware intros new GUI for mainframe tools
Beyond the GUI are plug-ins for data and debugging tools, as well as an OEM edition of Sli...
Black Hat conference fields suggestions for software security
Attendees give a wide variety of ideas about the subject, with Rex Black adding in some of...
Digg!  Digg
Reddit  Reddit
Slashdot  Slashdot
Share on facebook  Facebook
Share on Twitter  Twitter


            iphoneapp GET THE APP!

Why Some Developers Are Hurting SOA


By SD Times News Team
February 1, 2008 —  (Page 1 of 3)
Developers out there are not thinking about the architecture these days, generally speaking. They are so concerned about the next cool tool or language coming down the pike that architecture has a tendency to take a back seat.

There are a few exceptions. I’ve found in my tenure as CTO(s) that there are always those developers you find waiting for you in your office with great ideas around architecture. Those are meetings I always took, since developers typically have more insight into the systems and many of the suggestions I got from them over the years proved valuable.

However, another hard truth is that most developers don’t think about architecture, but focus more on the latest tools, languages and platforms. They are more concerned about how things are built, versus why they are built, or, more importantly, how software systems work and play well with other systems. That thought pattern needs to come to a quick end.

I’m finding that many developers who should actually understand and promote SOA are more of an obstacle, typically not thinking holistically about the purposes and placement of their software systems within the enterprise architecture. This is most troubling when you consider that the disciplines behind SOA, the exposure and development of services for reuse, benefit the developers most by providing cost-effective and quick mechanisms for building software systems going forward.

There are a few things that developers need to look out for, including the issues around:

• Not invented here.

• Not my job.

• Not fun.

Not invented here refers to the fact that many developers don’t like using OPC (other people’s code), and thus don’t like to leverage services. We saw this in the object-oriented days of the past, when reuse failed due to lack of interest, more so than lack of need.

While developers should indeed love creating their own software, working in isolation never benefits the more strategic good. Thus, you need to dump that attitude that others can’t build software as well as you. Thus, you need to learn how to use OPC and share your own. That’s the only way we’re going to get out of this architecture quagmire and move towards SOA.


Pages 1 2 3 


Share this link: http://www.sdtimes.com/link/31673
 

Add comment


Name*
Email*  
Country     


  • Comment
  • Preview
Loading



 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 
Download Current Issue
ISSUE 8/1/2010 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
blogs tab
Like Ruby n' Rails
Programming languages and Web frameworks go together like peas n carrots. Or Ruby n' Rails.
07/30/2010 04:36 PM EST

Adobe buys a Web-based IDE
Adobe looks to buy a rapid and agile Web development environment.
07/28/2010 03:49 PM EST

OpenStack opens up
OpenStack looks to be an intriguing new idea for running clouds.
07/28/2010 01:56 PM EST

 

Events calendar tab
SHARE
8/1/2010 to 8/5/2010
Boston
SHARE

VSLive
8/2/2010 to 8/6/2010
Redmond, Wash.
1105 Media

Agile 2010
8/9/2010 to 8/13/2010
Orlando
Agile Alliance

Delphi Live
8/23/2010 to 8/26/2010
San Jose
S&S Media

VMworld
8/30/2010 to 9/2/2010
San Francisco
VMware