Scribd
Upload
35 views24 pages

ITC4205 Lecture 2

This document provides an overview of a course on cloud computing and service-oriented architecture (SOA). It discusses why SOA is useful for innovation through loose coupling and reusability. The key components of SOA are services, service providers, service clients, and service registries. Web services use XML and HTTP to allow applications to communicate over the internet. Services have properties like being self-contained and representing business activities. Discovery of services is facilitated by UDDI registries.

Uploaded by

aabdurrahaman647
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
35 views24 pages

ITC4205 Lecture 2

This document provides an overview of a course on cloud computing and service-oriented architecture (SOA). It discusses why SOA is useful for innovation through loose coupling and reusability. The key components of SOA are services, service providers, service clients, and service registries. Web services use XML and HTTP to allow applications to communicate over the internet. Services have properties like being self-contained and representing business activities. Discovery of services is facilitated by UDDI registries.

Uploaded by

aabdurrahaman647
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 24

ITC4205: Introduction To

Cloud Computing
Time: Thursdays (10am to 12pm)
Course Lecturer: Umar Shafiu Haruna
Today’s Lecture (Note)
Why Service-Oriented Architecture (SOA)?
What is SOA?
SOA Building Blocks
• Service Provider
• Service Client
• Service Registry
Advantages of SOA
Services and their Properties
Web Services and Web Service Protocol Stack
Why SOA?
• Today’s world is all about Innovation. It is a process of making
changes in order to do something new.
• SOA greatly supports innovation through making changes easier.
• Traditionally building IT requires rigidly assembling hardware,
software and networking. Implementing change is tedious.
• With SOA, IT is build with easy to assemble and easily reconfigurable
components. These components are services like: checking inventory
and checking shipping status.
• You can assemble these services in any way you want.
• To make changes, simply rearrange them, add or remove others.
Saves time and money.
• This helps your business grow efficiently
• Also, flexibility to change makes your business innovate
Why SOA?
• Traditional engineering systems are homogeneous, bounded,
monolithic and relatively static. It is very hard to change large and
monolithic programs, hence makes it very difficult to change business
processes to meet new requirements or take advantages of new
business opportunities.
• This kind of systems can not read or exchange information with each
other, hence integrating these applications is cost ineffective. SOA can
save integration costs.
• Summarily, These kind of systems have the following issues
 Monolithic
 Extremely complex
 Very tightly coupled
 Difficult to identify perfect integration points
 Rigid architecture makes even small changes challenging, complex and costly
Why SOA?
• Most of the today’s business systems are complex engineering ones
that can be characterized as distributed, heterogeneous, dynamic,
unbounded.
• Modelling and Designing these systems requires an alternative
paradigm that deals with the following features:
 Focus on services rather than components
 Interoperability and cross platform to deal with high level of diversity
between components
 Loose coupling and distributed
 Abstraction against complexity
• This is the idea behind SOA.
An Example from IT
Development of transportation network application
Some of the requirements:
• Map for navigation
• Payment
• Login and authentication
• Etc.
Approaches to solving this problem:
1. Develop all the requirements as subsystems and finally integrate them.
Inefficient and cost ineffective
2. Use SOA. For example, use google map for the map, paypal as payment
gateway, etc. These are all services that can be integrated to achieve this.
Is SOA good enough???
What is SOA?
• Style of software design where services are provided to other
components through a communication protocol over a network
independent of vendors, products and technologies
• An IT architecture composed of software that has been exposed as
Services, that is, invoked on demand using a standard communication
protocol
• The goal is just-in-time integration of applications by discovering and
orchestrating network-available service.
• With this, applications will no longer be a big chunk of software that
runs on a computer but a combination of web services.
publish-find-bind paradigm
SOA is based on publish-find-bind paradigm
SOA Building Blocks
• Service Provider
 Provides service implementation
 Supplies service descriptions
 Provides related technical and business support
• Service Client
 Discovers and uses a service
• Service Registry
 Directory where service descriptions can be published and found
Advantages of SOA
• Reuse of services
• Business services across platforms
• Location independence
• Search and connectivity is dynamic
• No need for a particular network system
• Ability to more quickly meet customers demand
• Reduced reliance on custom development
• Allow businesses to be ready for the future
• Easier to integrate
Disadvantages of SOA
Reading Assignment
What is a service?
• Unit of work done by a service provider to achieved desired results
for clients (service consumers).
• It can also be defined as a logical manifestation of some resource
combined with some business logic.
• Service Providers provides the implementation and maintenance of
services
• Services are reusable
• Examples: Fund withdrawal or funds deposit service
Service Client and Service Provider Views
Properties of Services
• Self contained
• Represents business activities with specified outcome
• Black box for consumers (clients)
• It may consists of other underlying service

Services are separately maintained and deployed by developers.


Web Services
• Web services are a relatively new technology that have received wide
acceptance as an important implementation of service-oriented
architecture.
• This is because Web services provides a distributed computing
approach for integrating extremely heterogeneous applications over
the Internet
• Web services allows applications to talk to each other through XML-
based message exchange via Internet-based protocols
Web Service
Any service that is available via the Internet that is:
• Independent of OS, Platform, programming language and tools used
• Based on accepted open standards (seen to be XML)
• Self describing: Human or machine readable interface is available
• Discoverable: information on finding service is public
• Basic Web services combine the power of two ubiquitous
technologies: XML, the universal data description language; and the
HTTP transport protocol widely supported by browser and Web
servers.
Web services = XML + transport protocol (such as HTTP)
Web Service Protocol Stack
It is sometimes referred as WS Architecture
Web Service Protocol Stack
• XML Messaging Layer
• Web Services rely on SOAP for communication
• SOAP stands for Simple Object Access Protocol or SOA Protocol
• It is an XML-based communication protocol for exchanging messages
• It is independent of OS, programming environments and object model
framework
• It covers rules for processing messages
• It describes how to pack a message into an XML document
• It describes how to transport messages
• SOAP has SOAP header (containing generic, non-application dependent
information such as coordination information and security certificates) and
SOAP body (intended for application specific data).
SOAP Nodes and Message Path
Web Service Protocol Stack
• Description Layer
• Achieved using Web Service Description Language (WSDL)
• WSDL is a descriptive interface and protocol binding language
• WSDL covers:
• Type system
• Operations
• Interface
• Message exchange patterns
• Binding to transport protocol
Web Service Protocol Stack
• Discovery layer
• Service Discovery is the process of locating web service providers and
retrieving published web services descriptions.
• This involved querying service registry.
• After discovery, the developer or client should know:
• The service URI
• Its capabilities, and
• How to interface with it.
Finding Service
UDDI
• Universal Description, Discovery, and Integration (UDDI), a registry
mechanism that can be used to look up Web service descriptions
• UDDI
Universal: anyone with computer can use registry. It is based on standards
open to all: HTTP, XML
Description: Registry must provide some form of description that is human
or machine readable
Discovery: can be lookup by name or category.
Integration: WS should integrate into applications regardless of platforms
• Core Technologies used are: TCP, HTTP, HTTPS, XML and XML schema,
WSDL and SOAP

You might also like