SOA for SOA's sake

Too many times, we’re engaging in SOA for SOA’s sake. There are many situations were SOA may simply not be necessary. A mainframe system that rapidly processes transactions may be well enough left alone. You’re not going to increase the speed of systems by putting a layer on top of it. SOA success means applying SOA where needed. But if it ain’t broke, don’t fix it. Last month I was at a DoD seminar and one of the speakers said that you don't want to wrap a nuclear bomb system in a layer of SOA. That's good. I am glad the speaker (and hopefully others within DoD) realize this.