Skip to main content

Home/ ncushu/ Group items tagged soap

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Wesley Shu

» The story of Web 2.0 and SOA continues - Part 1 | Enterprise Web 2.0 | ZDNe... - 0 views

blogs.zdnet.com/Hinchcliffe

ajax astoria collective_intelligence granularity hinchcliffe mashup participation ria soa soap web2.0

shared by Wesley Shu on 05 Jun 07 - Cached
  • Web 2.0 and SOA really are largely (but not 100%) the same concepts that merely lay on different — if fairly different — parts of the software continuum
  • SOA is the dominant design paradigm in business software today
  • The core principle of SOA is the decomposition of software into sets of services which can be used and composed into new applications that have a very high level of integration and reuse.
  • ...13 more annotations...
  • 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
Wesley Shu

ABC: An Introduction to SOA - 0 views

www.cio.com/40941

soa

shared by Wesley Shu on 02 May 07 - Cached
  • service-oriented architecture is a strategy that proclaims the intention to build all the software assets in the company using the service-oriented programming methodology
  • Services are software chunks, or components, constructed so that they can be easily linked with other software components. The idea behind these services is simple
  • the only difference is that today, the ambition for the size and sophistication of these software objects is far more grand.
  • ...3 more annotations...
  • 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.
1 - 2 of 2
Showing 20▼ items per page