What's the next frontier for SOA?Add to Apr. 16, 2008 It took us about twenty years for enterprise databases to achieve a certain degree of reliability and scalability, combined with a level of security that is deemed acceptable for most applications and in most instances. However, applying some lessons learned in the past certainly can't hurt either. Compared to database transactions, SOA (Service Oriented Architecture) could involve in some cases a far more complicated scenario. To begin with, there’s the basic architecture, which calls for a middle tier abstraction layer that separates the Web service from whatever physical systems implement it.  Some could argue that the days of transaction processing introduced its own middleware: transaction monitors. Nonetheless, given the dynamic nature of SOA it could make delivering ACID reliability for run-of-the-mill OLTP systems appear to be too easy... Most of the time, troubleshooting it could require serious analyzis work. For example, when a customer's service is composed from order history and account identifiers in ERP, and interaction history from CRM, where do you start looking when the service fails to execute? SOA generally integrates rather well in large systems, but the world of run-time governance of SOA still remains very fragmented. There’s yet another parallel between SOA and the evolution of databases. Back in 1988, there were debates over whether SQL databases could handle the load and deliver the performance of legacy databases or file systems. Naturally, the answer was throwing Moore’s law at the problem...  Nowadays, there are similar questions regarding SOA, because if Web services standards are met, that means a lot resource-hungry XML messages scurrying around everywhere. One answer is that there’s a glut of underutilized processing capacity out there and a crying need for virtualization software to make that iron available for XML. To be sure, some contend that SOA brings pressure on various systems and APIs using Service Component Architecture and Service Data Objects. It also points to new competition for where new functionality gets implemented inside the application stack. The question of who wins or loses when you add SOA to the mix is rather irrelevant. The inference is that some solutions might be supersets of various applications, and thanks to SOA, far more dynamic. However, what about the other half of the enterprise market that uses in-house rather than commercial software? To many industry observers and from a technology standpoint, SOA might be undergoing even more changes, but more and more outcomes to vendor's business relationships are expected nevertheless. Add to
Source: Web Services.org  Have your website professionally optimized by the search engine positioning experts at Rank for $ales. Get your business or company listed in the Global Business Listing directory and increase your business. It takes less then 24 hours to get a premium listing in the most powerful business search engine there is. Click here to find out all about it. For the best technical information on hardware, software, Internet applications, e-Commerce, B2B, Web services or IT-related industry news, visit Tech Blog.
Sponsored by
Internet Trends
Sponsored by
LCWHG
Sponsored by
ISEN 
|
Digg this
