XML: The Three Revolutions

Slides:



Advertisements
Similar presentations
웹 서비스 개요.
Advertisements

Siebel Web Services Siebel Web Services March, From
Overview of Web Services
Web Service Ahmed Gamal Ahmed Nile University Bioinformatics Group
Service Oriented Architecture Terry Woods Session 50.
Snejina Lazarova Senior QA Engineer, Team Lead CRMTeam Dimo Mitev Senior QA Engineer, Team Lead SystemIntegrationTeam Telerik QA Academy SOAP-based Web.
CSIS0402 System Architecture K.P. Chow University of Hong Kong.
I.1 Distributed Systems Prof. Dr. Alexander Schill Dresden Technical University Computer Networks Dept.
Presentation 7 part 1: Web Services Introduced. Ingeniørhøjskolen i Århus Slide 2 Outline Definition Overview of Web Services Examples Next Time: SOAP.
Presentation 7: Part 1: Web Services Introduced. Outline Definition Overview of Web Services Examples Next Time: SOAP & WSDL.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
SOA with Progress Philipp Walther Consultant. © 2007 Progress Software Corporation2 Agenda  SOA  Enterprise Service Bus (ESB)  The Progress SOA Portfolio.
Notes to the presenter. I would like to thank Jim Waldo, Jon Bostrom, and Dennis Govoni. They helped me put this presentation together for the field.
CSC-8530: Distributed Systems Christopher Salembier 28-Oct-2009.
A New Computing Paradigm. Overview of Web Services Over 66 percent of respondents to a 2001 InfoWorld magazine poll agreed that "Web services are likely.
DCS Architecture Bob Krzaczek. Key Design Requirement Distilled from the DCS Mission statement and the results of the Conceptual Design Review (June 1999):
1. Introducing Java Computing  What is Java Computing?  Why Java Computing?  Enterprise Java Computing  Java and Internet Web Server.
Web Services Andrea Miller Ryan Armstrong Alex. Web services are an emerging technology that offer a solution for providing a common collaborative architecture.
2006 IEEE International Conference on Web Services ICWS 2006 Overview.
Ch 12 Distributed Systems Architectures
JMS Java Message Service Instructor Professor: Charles Tappert By Student: Amr Fouda.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 2 – Components.
© Prentice Hall CHAPTER 3 Computer Software.
Systems Architecture, Fourth Edition1 Internet and Distributed Application Services Chapter 13.
Web Services Michael Smith Alex Feldman. What is a Web Service? A Web service is a message-oriented software system designed to support inter-operable.
By Justin Thompson. What is SOAP? Originally stood for Simple Object Access Protocol Created by vendors from Microsoft, Lotus, IBM, and others Protocol.
Rawlins EDI Consulting1 Future EDI - What comes after X12 and EDIFACT? Michael C. Rawlins.
Introduction SOAP History Technical Architecture SOAP in Industry Summary References.
Web Services Mohamed Fahmy Dr. Sherif Aly Hussein.
1 Web Services Distributed Systems. 2 Service Oriented Architecture Service-Oriented Architecture (SOA) expresses a software architectural concept that.
Middleware-Based OS Distributed OS Networked OS 1MEIT Application Distributed Operating System Services Application Network OS.
Web Services Architecture1 - Deepti Agarwal. Web Services Architecture2 The Definition.. A Web service is a software system identified by a URI, whose.
Jaeki Song ISQS6337 JAVA Lecture 16 Other Issues in Java.
UNIT – II ARCHITECTING WEB SERVICES. WHAT ARE WEB SERVICES ? Web Services are loosely coupled, contracted components that communicate via XML-based interfaces.
11/16/2012ISC329 Isabelle Bichindaritz1 Web Database Application Development.
What is Service Oriented Architecture ? CS409 Application Services Even Semester 2007.
第十四章 J2EE 入门 Introduction What is J2EE ?
Lecture 15 Introduction to Web Services Web Service Applications.
1 Introduction to Middleware. 2 Outline What is middleware? Purpose and origin Why use it? What Middleware does? Technical details Middleware services.
Based on the paper “Myths around Web Services” by Gustavo Alonso Web Services & Myths Around it Debashis Roy Deepa Saha.
SOAP TECHNOLOGY What is SOAP ? SOAP is a simple, lightweight XML protocol for exchanging exchanging structured and typed information on the Web Extensible.
Introduction to Server-Side Web Development Introduction to Server-Side Web Development using JSP and Web Services JSP and Web Services 18 th March 2005.
WebService. Outline Overview of Web Services SOAP (messaging) WSDL (service description) UDDI (registry)
XML and Web Services (II/2546)
May 2003National Coastal Data Development Center Brief Introduction Two components Data Exchange Infrastructure (DEI) Spatial Data Model (SDM) Together,
CORBA1 Distributed Software Systems Any software system can be physically distributed By distributed coupling we get the following:  Improved performance.
Presented By:- Sudipta Dhara Roll Table of Content Table of Content 1.Introduction 2.How it evolved 3.Need of Middleware 4.Middleware Basic 5.Categories.
S imple O bject A ccess P rotocol Karthikeyan Chandrasekaran & Nandakumar Padmanabhan.
Kemal Baykal Rasim Ismayilov
1 Object Oriented Logic Programming as an Agent Building Infrastructure Oct 12, 2002 Copyright © 2002, Paul Tarau Paul Tarau University of North Texas.
SOAP-based Web Services Telerik Software Academy Software Quality Assurance.
An Introduction to Web Services Web Services using Java / Session 1 / 2 of 21 Objectives Discuss distributed computing Explain web services and their.
CSCE 315 – Programming Studio Spring Goal: Reuse and Sharing Many times we would like to reuse the same process or data for different purpose Want.
Service Oriented Architecture + SOAP -Robin John.
Web Services An Introduction Copyright © Curt Hill.
1 Distributed System using J2EE. 2 What is J2EE?  J2EE (Java2 Enterprise Edition) offers a suite of software specification to design, develop, assemble.
Electronic Commerce Semester 1 Term 1 Lecture 7. Introduction to the Web The Internet supports a variety of important tools, such as file transfer, electronic.
Web Services. Web Service: Simple definition : “ Service Offered On the Web “ Technically : “ A Web Service is a programmable application component that.
XML— “Oxygen for E-Business” Persistent eBusiness Solutions Pvt. Ltd. Arvind Pandey
E-commerce Architecture Ayşe Başar Bener. Client Server Architecture E-commerce is based on client/ server architecture –Client processes requesting service.
A service Oriented Architecture & Web Service Technology.
Service Oriented Architecture (SOA) Prof. Wenwen Li School of Geographical Sciences and Urban Planning 5644 Coor Hall
The Object-Oriented Thought Process Chapter 13
Sabri Kızanlık Ural Emekçi
Distribution and components
Inventory of Distributed Computing Concepts and Web services
Inventory of Distributed Computing Concepts
Service Oriented Architecture + SOAP
Enterprise Resource Planning
Enterprise Resource Planning
Presentation transcript:

XML: The Three Revolutions

Three Revolutions The three revolutions: data, architecture, and software. Data, which XML frees from the confines of fixed, program-dependent formats. Architecture, with a change in emphasis from tightly coupled distributed systems to a more loosely coupled confederation based on the Web Software, with the realization that software evolution is a better path to managing complexity than building monolithic applications.

Data Revolution Prior to XML, data was very much proprietary, closely associated with applications that understood how data was formatted and how to process it. Now, XML-based industry-specific data vocabularies provide alternatives to specialized Electronic Data Interchange (EDI) solutions by facilitating B2B data exchange and playing a key role as a messaging infrastructure for distributed computing.

Data Revolution XML’s strength is its data independence. XML is pure data description, not tied to any programming language, operating system, or transport protocol. XML is a subset of SGML designed to facilitate the exchange of structured documents over the Internet. The designers of XML took the best parts of SGML and, based on their experience, produced a technology comparable to SGML but much simpler to use.

Data Revolution XML comes out of a document culture that is distinct from the code and data cultures that are the hallmarks of the mainstream computer industry. The code culture is characterized by a focus on programming languages, beginning with FORTRAN and evolving through Algol to C, C++, and Java. The data culture is characterized by COBOL, data processing, and databases. From a code perspective, data is something to be transported by procedure calls. From a data perspective, data is something to be stored in databases and manipulated.

The late 1980s and early 1990s saw code and data combine in the form of object- oriented languages such as C++, Smalltalk, Java, and Object COBOL Infrastructures such as CORBA, DCOM, and Enterprise JavaBeans (EJB) provide interconnection, security, and transaction- based services for extending the enterprise. What XML brings to the computing world is a technology that allows data to be freed from the constraints created by code-centric infrastructures.

It allows code to be treated as data, which has been the driving force behind using XML for remote procedure calls. XML offers an alternative to both EDI and technologies such as CORBA, RMI, and DCOM that lock data transfer into underlying networks and object infrastructures.

The Architectural Revolution The focal point of the change in architectural thinking has been a move from tightly coupled systems based on established infrastructures such as CORBA, RMI, and DCOM, each with their own transport protocol, to loosely coupled systems riding atop standard Web protocols such as TCP/IP. Drawback of CORBA, RMI and DCOM is their inability to communicate with other tightly coupled systems or directly with the Web.

Loosely coupled Web-based systems provide universal connectivity. Using TCP/IP as the transport, systems can establish connections with each other using common open-Web protocols The loose coupling of the Web makes possible new system architectures built around message- based middleware or less structured peer-to-peer interaction.

The Software Revolution During the 1970s and 1980s, software was constructed as monolithic applications built to solve specific problems. The problem with large software projects is the software is often ill-suited to tackle multiple problems at once, adding new functionality and adapting to technological change

The Software Revolution In the 1990s a different model for software emerged based on the concept of simplicity. Instead of trying to define all requirements up front, this new philosophy was built around the concept of creating building blocks capable of combination with other building blocks that either already existed or were yet to be created.

The Software Revolution After decades of attempts to build complex infrastructures for exchanging information across distributed networks, the Web emerged from an assemblage of foundational technologies such as HTTP, HTML, browsers, and a longstanding networking technology known as TCP/IP. The Web is an example of the power of combination