The term service-oriented architecture gets thrown around a lot these days. We at SearchWebServices.com are as guilty of it as anyone, though to be fair it is what we cover. If we were SearchPizza.com we'd probably abuse words like sauce, crust and cheese.
Yet sometimes a term gets used so much that you can forget what it meant in the first place. Obviously there's the definition of SOA, which is always handy when you need some grounding, but say you want more. SOA has a set of principles, a new lifecycle, a different ROI proposition and it requires a new way of organizing your projects.
If you're going to marry your company to SOA shouldn't you take the time to really get to know it? While it can be argued that a shared love of blueberry pie and goofy YouTube videos are all it takes to form the basis of a meaningful human relationship, a deeper level of familiarity is probably in order.
