ServiceOriented Architecture (SOA) vs. （ServiceOriented的体系结构(SOA)。）.pdfVIP

Service-Oriented Architecture (SOA) vs. Component Based Architecture Helmut Petritsch Service-oriented architecture (SOA) vs. Component based architecture 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 Helmut Petritsch 2/14 Service-oriented architecture (SOA) vs. Component based architecture Introduction SOA is a buzzword and topic for many discussions in nearly every professional journal and conference. Opinions differ from “some technical rubbish” to “the technology of the future”. The problem about these different opinions partly depend on another problem: What precisely is SOA? Whatever it is and will be, it seems to become the next step in the evolution of software architecture. Probably SOA is mostly linked with Web Services: They are mostly used to open existing architectures and systems on specific points and allocate them via HTTP or HTTPS. 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 idea results in the (old) idea, of building a “legobox” of interoperable, reusable services.