Group items tagged

SOA and Web 2.0 have also crossed over considerably around Rich Internet Applications and Ajax.

Web-Oriented Architecture

SOAP is not Web-oriented

but competing protocols such as REST, and now ATOM, are very clearly Web-oriented

This is one reason that Google got rid of its SOAP search API

Project Astoria, downloadable today in CTP form here, makes it possible to expose almost any ADO-compliant database as a set of granular, queryable URLs in simple REST form.

Project Astoria

there are literally thousands of software platforms and enviroments that presently exist in the world. And if they don’t speak your unique flavor of SOA (SOAP and WS-*), interopability with them won’t (and doesn’t) happen.

With WOA, anyone that can speak HTTP — the fundamental protocol of the Web — and anyone that can process XML, which is to say just about every tool and platform that exists today, can interoperate and work together simply, safely, and easily and build applications on top of one another services.

Importantly, mashups are a key outcome of the trend towards WOA and most mashups are based on REST or REST-like services.

Astoria is a solid example of how major software companies are now committing serious and disciplined effort to “WOA-ify” our traditional enterprise datastores

2. A better way to sell architecture to the business (and IT).

It means business people can visualize, for the first time, how their businesses are constructed in terms of technology.

When IT projects are put in terms of business activities and processes rather than complex software applications, business people can better appreciate and support IT projects

Reuse, improved productivity and agility in IT and a software infrastructure tuned to specific business processes

Developers create the abstraction by building a complex wrapper around the bundled code. This wrapper is an interface

use the simple object access protocol (SOAP) to build a single link to the carefully crafted interface that wraps around the service

For example, at telecom company Verizon, the service called "get CSR" (get customer service record) is a complex jumble of software actions and data extractions that uses Verizon's integration infrastructure to access more than 25 systems in as many as four data centers across the country. Before building the "get CSR" service, Verizon developers who needed that critical lump of data would have to build links to all 25 systems—adding their own links on top of the complex web of links already hanging off the popular systems. But with the "get CSR" service sitting in a central repository on Verizon's intranet, those developers can now use the simple object access protocol (SOAP) to build a single link to the carefully crafted interface that wraps around the service >. Those 25 systems immediately line up and march, sending customer information to the new application and saving developers months, even years, of development time each time they use the service.

ERP of IT”可以從技術和標準兩個維度來進行分析

技術方面，ERP軟體廠商、中間件廠商和作業系統軟體廠商的軟體構建方法開始從各自不同實現技術向趨同的標準演化

在標準方面，ITSM、IT Governance和ITIL等理論框架的不斷成熟，讓IT部門進一步專業化分工，組織行為進一步“企業化”。