This post originated from an RSS feed registered with Java Buzz
by Vinny Carpenter.
Original Post: Microsoft Architect Touts SOAs -
Feed Title: Vinny Carpenter's Blog
Feed URL: http://www.j2eegeek.com/error.html
Feed Description: Welcome to my blog. I am a total Java geek that lives in Milwaukee, making my living as an architect/developer, spending all my time with Java, J2EE, OO, Linux, and open source. In my spare time, when I am not in front of my computers, I spend every other minute with my other loves: My wife, books, music, guitars, Formula-1 racing and StarGate. Check out my blog @ http://www.j2eegeek.com/blog
ok. What's the point of this article? Isn't talking about interfaces vs. implementation like comparing apples to oranges? The idea of services and decoupling systems to reduce cohesion makes sense and people are doing that. However, SOA and OO aren't mutually exclusive.
In my world of SOA, services have published interfaces that are de-coupled from the applications that use them and deployed to allow maximum reuse, regardless of the programming language, application server, etc. used. Nothing in that precludes me from using objects in building the coarse-grained business process that I am exposing as a service.
To play devil’s advocate, I could argue that SOA means we don’t care about how we build the guts of the service as long as the piece of functionality is exposed as a service. But what about objects, encapsulation, inheritance, and polymorphism? Isn’t the goal of OOP to simplify our lives and make software maintenance easier?
I've actually had the pleasure of meeting Don Box and he is really a brilliant guy. I'm wondering if he really believes this or did eWeek made up the whole thing. Who knows? It was interesting to see that the last line of the article was 'Box said he based his presentation on a new book he has in the works'. Hmmm.. Maybe Don's trying to get some buzz started about his new book :)
Previous Topic
