This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: The Rocky Road to SOA
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.
Yesterday I tuned into Rocky Lhotka's webcast on design and architecture for .Net apps. He went through that basic N-Tier concepts, explaining each thoroughly and giving quality examples. The main thing I learned was how to actually teach this material.
His comments on SOA, though, are less to my liking. The dismissal of SOA for intra-app development is, IMO, premature. The basis of his argument is that to take the existing tiers and separate them by trust boundaries would be folly.
I whole-heartedly agree !
The tiered architecture can't be just wrapped up in web services and called SOA !
What's needed is a total re-architecture of the system in order to utilize SOA's strengths.
While I'm still waiting to hear from Rocky on this, I'll give an example where both he and I see eye to eye: Rocky espouses the use of a "data portal" to handle all issues with databases, abstracting away issues of database location, and communication through remoting, or through firewalls. I suggest using a Persistence service in SOA that does the exact same thing! Maybe, just maybe, we're all talking about the same thing, but just calling it different names.
Previous Topic
