Guest View: Sometimes, slower is better



Email    print   
February 3, 2009 —  (Page 1 of 3)
New technology for simplifying development is always good, right? New APIs and servers just make it easier to develop SOA applications, right? And, of course, developers have all the time they need to adjust to the big changes that SOA development imposes on them.

Of course, this isn’t true. With any technological change as important—and beneficial—as the shift to SOA, it takes time for developers and businesses to absorb the important standards, to implement them in real applications and to get comfortable with the impact of SOA on the overall development environment. In short, it is important for vendors to release technology on a schedule that makes it possible for users to consume the technology, and to support it in ways that allow developers and businesses to recoup their investments in those products.

Michael Rowley
Recent announcements from Microsoft got me thinking about the tension between a vendor's desire to create new development technology and the developer's desire for predictability in the pace of change for the technologies they use to accomplish their work.

Microsoft will soon be releasing Workflow Foundation (WF) 4.0, which will have some big changes from previous versions, primarily for the purpose of simplifying development. There will now be a flowchart workflow style, which will join the sequential and state machine workflow styles that already exist.

WF will be integrated with the Windows Communication Framework, and developers will be able to deploy the resulting Web-service enabled workflows to the “Dublin” application server. So the first question that comes to mind is, if you can develop Web-service-enabled flowcharts using WF and deploy them to Dublin, how many people will still be interested in buying BizTalk Server? Actually, that is just a question for Microsoft product management to worry about. I’ve got bigger questions.

How many technologies do we need to accomplish the same thing? How many times can Microsoft add a new technology for simplifying development before the number of simplifying technologies becomes just too complex to follow? Once we have learned the latest-and-greatest way of developing apps, how long should we be able to expect that knowledge and those skills to be relevant? And what about the code and other artifacts? Even if there is an attempt to continue to execute code from older versions, it is hard for any vendor to provide comprehensive forward-compatibility for abandoned products.



Related Search Term(s): SOA, software development, standards, Microsoft

Pages 1 2 3 


Share this link: http://sdt.bz/33236
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Microsoft's plans for post-Windows OS revealed
A componentized non-Windows operating system is in the works at Microsoft, one that could eventually phase out Windows. The OS features asynchronous-only architecture built for task concurrency Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb