Why Adopting SOA Is Like Purchasing a Total Gym
I liken new trends in software development and architecture to the late-night Total Gym ads that feature Chuck Norris and Christie Brinkley. After forsaking sleep and an hour of my time (that I will never get back) I have learned the benefits of the Total Gym. It only takes 30 minutes a day, they claim, and I will be fit as a fiddle. I will look just like Chuck (although not really. He's short. I met him once and was quite surprised. I even thought for a moment I could kick his butt...but I digress).
The fact is, the Total Gym isn't going to do much for me, in and of itself. For the equipment to be effective, I need to learn proper technique for each exercise. I need to create an effective workout plan. I need to execute the workout plan. I need to rest and to allow my body to rebuild muscle tissue. Oh, and I need to stop eating entire bags of M&Ms while I code and learn to gulp down a green leafy vegetable or two. A little more sleep wouldn't hurt, either.
To get to my point...I have to change my lifestyle if I want to lose those extra pounds.
Adopting SOA Isn't Enough
Service-oriented architecture is among the latest "Total Gyms" trumpeted in software development circles. SOA promises tons of benefits and is certain to provide positive results for your IT organization.
But the purchase of a Total Gym will not make you as tough as Chuck Norris or as nice-looking as Christie Brinkley. And simply adopting SOA will not trim the fat from your architecture designs; nor will it instantly improve the way you develop and deliver software. Far from it, in fact.
Adopting SOA is lifestyle change that has to become integrated into all aspects of your culture, including business processes, software requirements development, software architecture, software development lifecycle, project management, and hardware and software purchases.