Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
7Activity
0 of .
Results for:
No results containing your search query
P. 1
SOA vs component based

SOA vs component based

Ratings:
(0)
|Views: 458|Likes:
Published by Rajesh Ranjan
Difference b/w SOA and Component based
Difference b/w SOA and Component based

More info:

Published by: Rajesh Ranjan on Jan 20, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

01/17/2011

pdf

text

original

 
 
Service-Oriented Architecture (SOA)vs. Component Based Architecture
Helmut Petritsch
 
Service-oriented architecture (SOA) vs. Component based architecture
Helmut Petritsch 2/14
 
Index
Introduction..................................................................................................3
 
Definitions....................................................................................................3
 
Component-based architecture:....................................................................3
 
Service-oriented architecture (SOA)...............................................................4
 
Evolution vs. revolution................................................................................6
 
Loose Coupling and the possibility of publication.................................................8
 
What’s new about SOAP?..............................................................................8
 
Why not CORBA for SOA?.............................................................................9
 
SOA and SOAP............................................................................................9
 
Confine SOA vs. components........................................................................9
 
SOA a miracle cure?...................................................................................11
 
Gained Web Services mean bad performance................................................11
 
A jungle of standards doesn’t make it easy...................................................11
 
Finding the right Web Services....................................................................12
 
Are there guarantees for Web Service users?................................................12
 
Quality of Service of foreign applications......................................................12
 
Data overhead and lower performance though XML/SOAP...............................13
 
Conclusion...................................................................................................14
 
 
Service-oriented architecture (SOA) vs. Component based architecture
Helmut Petritsch 3/14
 
Introduction
SOA is a buzzword and topic for many discussions in nearly every professional journal and conference. Opinions differ from “some technical rubbish” to “thetechnology of the future”. The problem about these different opinions partly dependon another problem: What precisely is SOA? Whatever it is and will be, it seems tobecome the next step in the evolution of software architecture.Probably SOA is mostly linked with Web Services: They are mostly used to openexisting architectures and systems on specific points and allocate them via HTTP orHTTPS. This procedure features mainly one thing: An easy way of B2B connection.Because of the loose coupling of Web Services are optimal for reuse. This idearesults in the (old) idea, of building a “legobox” of interoperable, reusable services.All we need next is an architecture that allows to composite the existing Services.And this architecture could be SOA.But wait: Module, composition, reusability: Isn’t that an old hat? What’s thedifference to Enterprise Java Beans or component based architecture? Isn’t that thesame idea? It probably is. But there are a few details, which make a big difference.This paper has been written to figure out these differences.
Definitions
Component-based architecture: 
A component is a software object, meant to interact with other components,encapsulating certain functionality or a set of functionalities. A component has aclearly defined interface and conforms to a prescribed behaviour common to allcomponents within an architecture.
1
 The goal of generative and component-based software engineering is to increaseproductivity, quality, and time-to-market in software development thanks to thedeployment of both standard componentry and production automation. Oneimportant paradigm shift implied here is to build software systems from standardcomponentry rather than "reinventing the wheel" each time. This requires thinking interms of system families rather than single systems. Another important paradigm
1
 http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211/ 

Activity (7)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
suridb liked this
pranay1507 liked this
pranay1507 liked this
Alpa Ved liked this
tungfpt liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->