Big SOA/Little SOA
My Google Alert for SOA brought quite an interesting blog hit today, from Neil Macehitter and Neil Ward-Dutton. Entitled Big SOA vs Little SOA, it is a great discussion of the difference between companies using service oriented architecture to change their entire way of doing business, versus those who just use it to build somewhat less chaotic software. The interesting thing is that information management hasbecome some criticalto how companies operate that it is quite possible that it has the same amazing "ripple effects" (think stone in a smooth pond) that financial management traditionally had.
In the same way that accounting rules and tax policy can encourage/discourage certain kinds of capital spending, the way an enterprise or organization architects its services could change its business model. The most common place I personally see this (no surprise...) is in B2B. Some companies practice "little B2B", which is mostly centered on either complying to partners' needs or lowering costs, while other companies practice "Big B2B", which is focused on leveraging their partners strengths andknowledge andbeing easy to do business with. Earlier I tended to call these tactical and strategic B2B, but I like the little/big nomenclature better.






