This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Further Thoughts on SOA
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
Maybe, as Brian Noyes points out, SOA is “a further evolution down that path - encapsulating functionality and processes at a course grained level - making it easier to describe and compose larger systems out of collaborating, interrelated parts.” Proclaiming the death of objects was an unfortunate miststatement on my part. I really meant OOA/OOD - how do you now design/decompose system design/requirements into architectures and I think it's less now about classic OOA/OOD and tightly coupled object design and more about a loosely coupled collection of components under a service. Thats really what I meant in the paradigm shift - the shft for architecture design. You still use objects and especially components but you design your interfaces differently and you sure design your architectures differently. Am I making sense yet? I am still trying to figure this all out too with you all.
Previous Topic
