This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: Learn how to quickly convert your .NET Applications to Service Oriented Solutions w/NET 3.0
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
I just ran into this on the Public Sector DPE Team's blog: Learn how to quickly convert your .NET Applications to Service Oriented Solutions w/NET 3.0? (Web Cast) To me, it sounds like a serious downplaying of the 'A' part of SOA. Actually, I find this to be true around most of Microsoft's "Service Orientation" message. Remember how easy it was supposed to be to "convert" your apps from VB6 to .Net when it came out? Expect that to be peanuts compared to a move to SOA. Changing your app's communication to WCF won't improve your system's architecture by itself, let alone transform it to become business aligned (ughh, how I hate these marchitecture type words). If you haven't done the deep business analysis before developing your app, don't expect Indigo to magically make it happen, quickly or otherwise. I guess that I'm just sick of Microsoft spinning everything as "easy" and "quick". Nothing about our jobs are easy or quick, that's why we get "the big bucks" and these projects cost an arm and a leg....
Previous Topic
