"The soa [service oriented architecture] seeks to separate out the core functionalities needed by a number of different applications into a series of modular components, provided as loosely coupled services." So far so good. But then, "the functions or tasks need to be provided with an agreed-upon open interface, and the wider the agreement is on these tasks, the greater the market for such services and the lower the price." Um, hm. But then, "considerable time and effort of experienced and technically skilled people is needed to establish such agreements." Well, that's really going to favour the entities that can fund such people, isn't it? But I digress. This article describes, in very general outlines, the consequence of such work, the E-Framework.
Today: 2 Total: 16 [Direct link] [Share]
