Simon Johnston has a rather interesting developerWorks blog, Service Oriented Architecture and Business-Level Tooling. He hasn't had time to blog in a couple of months, but popped up again last week with a couple of interesting postings.
The first posting discusses a major advantge of SOA services, that a service's components and all their prerequisites are already hosted for you. Would you really want to host your own credit card validation component? What database would it work off of?
The second posting discusses the relationship of services, components, and objects. Also, does SOA encourage fewer connections, less distribution, and fewer dependencies between components, or more of them?
It's good to have Simon back.