Developers rule the world, everyone else is just domino effect – so I’d start with devs.

There are good reasons that I don’t write blogs, but since you asked (didn’t you?), I think a perspective in on management would be useful as well. If that’s a part of the business, cool. I’m thinking from the perspective of “If you had to pitch the concept of SOA to a group of all levels of IT management, right up to the CIO, how would you do it?”

Looking forward to hearing your thoughts, as usual.

-Chris

You certainly have an effect on people, but in this case you are not alone. SOA is not an easy topic to comprehend; regardless of what the SOA vendors are saying, it is not tangible. As Bill states in his response, we will cover this topic in some upcoming posts. We will shoot for next week at this point.

Thanks for checking in with us!
Brandon

W/R to your comment, not a step back at all. In fact, your comment gave me clarity on how to approach my next set of blogs which will cover “What’s in it for me” angle, where “Me” is the developer, the business, the DBA. Where do you want me to start?

This is probably a step back from where you started with this site, but I’ll ask anyway.

One of the main problems in getting an SOA effort off the ground (at least at my company) is that communicating the concept is difficult. Or maybe understanding the concept is difficult when you are hearing it for the first time.

Database folks seem to think you are talking about building a data warehouse. Developers seem to have trouble distinguishing SOA from “just a bunch of web services”. My legacy developers are scared and confused, and managers are just wondering who is going to pay for it, since it’s not their project.

Now, maybe I just have those effects on people, but I’m wondering if this might be a common thing that stops these types of efforts from ever going anywhere.

Any thoughts on communicating just exactly what SOA is to mixed audience of technical and non-technical folks, and how it will help them?