Criticisms of SOA

Some criticisms of SOA are founded on the assumption that SOA is right term for Web Services. For example, some criticisms claim results of SOA in the addition of the XML layers introducing XML parsing and composition. In the absence of the native or binary forms of Remote Procedure Call (RPC) applications could run slower and require more processing capacity, increasing costs. Most implementations do incur these overheads, but SOA can be implemented using technologies (for example, Java Business Integration (JBI)) which do not depend on remote procedure calls or translation through XML. At the same time, there emergent, of technologies of analysis of open-source XML, such as VTD-XML, and various XML-compatible binary formats which promise significantly to improve the execution of SOA. The services of Stateful require of the consumer and the provider to share the same consumer-specific context, which one or the other is included inside or referred by messages exchanged between the provider and the consumer. The disadvantage of this constraint is that it could reduce the total scalability of the service provider because it could have to remember the shared context for each consumer. It also increases the coupling between a service provider and a consumer and makes switching service providers more difficult.

Another concern is that WS standards and products are still evolving, and SOA can thus introduce new risks unless properly managed and estimated with additional budget and contingency for additional Proof of Concept work. Some critics feel SOA is merely an obvious evolution of currently well-deployed architectures. A SOA being architecture is the first stage to represent the components of system which connect together to the profit businesses. On this level a SOA is right an evolution of an existing architecture and businesses functions. SOA s is normally associated with interconnecting back end transactional systems that are accessed via web services. The genuine issue with any IT “architecture” is how one defines the information management model and operations around it that deal with information privacy, reflect the business’s products and services, permit services to be delivered to the customers, allow for self care, preferences and entitlements and at the same time embrace identity management and agility. On this last point, system modification is a serious issue which is generally omitted from IT system design. Many systems, including SOAs, hard code the operations, goods and services of the organization thus restricting their online service and business agility in the worldwide market place.

Updated: February 18, 2010 — 6:18 am © 2008 - 2017