Service-oriented architecture 8 th July 2013. What is a Service? A service is a reusable component that can be used as a building block to form larger,

Slides:



Advertisements
Similar presentations
REST Introduction 吴海生 博克软件(杭州)有限公司.
Advertisements

Service Oriented Architecture Terry Woods Session 50.
Building an Operational Enterprise Architecture and Service Oriented Architecture Best Practices Presented by: Ajay Budhraja Copyright 2006 Ajay Budhraja,
7-1 INTRODUCTION: SoA Introduced SoA in Chapter 6 Service-oriented architecture (SoA) - perspective that focuses on the development, use, and reuse of.
A Successful RHIO Implementation
Technical Track Session Service-Oriented Architecture Terry Woods.
Leveraging Technology to Enhance PeopleSoft Web Services (SOA) System Efficiency Lorne Kaufman, Managing Director.
1 Introduction to SOA. 2 The Service-Oriented Enterprise eXtensible Markup Language (XML) Web services XML-based technologies for messaging, service description,
Session 28 Techie Terminology and Benefits for Financial Aid Administrators Tim Bornholtz Holly Hyland.
© 2006 IBM Corporation IBM Software Group Relevance of Service Orientated Architecture to an Academic Infrastructure Gareth Greenwood, e-learning Evangelist,
Stuart Sim Chief Architect Global Education & research Sun Client Solutions Blog:
SOA Basics SSE USTC Qing Ding. Topics Quick introduction to SOA Composite applications Services and SOA.
Realising the Potential of Service Oriented Architecture Kris Horrocks Connected Systems Division Microsoft.
Page 1 Elements of Service-Oriented Architecture B. Ramamurthy.
CS 415 N-Tier Application Development By Umair Ashraf July 6,2013 National University of Computer and Emerging Sciences Lecture # 9 Introduction to Web.
SOA – Development Organization Yogish Pai. 2 IT organization are structured to meet the business needs LOB-IT Aligned to a particular business unit for.
SOA, BPM, BPEL, jBPM.
What is Enterprise Architecture?
UNIT – II ARCHITECTING WEB SERVICES. WHAT ARE WEB SERVICES ? Web Services are loosely coupled, contracted components that communicate via XML-based interfaces.
SAMANVITHA RAMAYANAM 18 TH FEBRUARY 2010 CPE 691 LAYERED APPLICATION.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 09. Review Introduction to architectural styles Distributed architectures – Client Server Architecture – Multi-tier.
Service Oriented Architecture (SOA) at NIH Bill Jones
Progress SOA Reference Model Explained Mike Ormerod Applied Architect 9/8/2008.
1 XML Based Networking Method for Connecting Distributed Anthropometric Databases 24 October 2006 Huaining Cheng Dr. Kathleen M. Robinette Human Effectiveness.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
AUTHORS: MIKE P. PAPAZOGLOU WILLEM-JAN VAN DEN HEUVEL PRESENTED BY: MARGARETA VAMOS Service oriented architectures: approaches, technologies and research.
Introducing Managed Services Wolf Gilbert Architect Evangelist Microsoft Corporation.
Service Oriented Architecture CCT355H5 Professor Michael Jones Suezan Makkar.
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
Service Oriented Architecture + SOAP -Robin John.
Advanced Web Technologies Lecture # 5 By: Faraz Ahmed.
1 SERVICE ORIENTED ARCHITECTURE ANTHONY GACHANGO D61/70547/2008 DIS 601.
Basics of SOA Testing Assurance Services Unit 24 February 2016.
SOA & Event Driven Architecture Steve Else, Ph.D., Certified Enterprise Architect, SOA COP Srinidhi Boray, Certified Enterprise Architect, Ingine, Inc.
Introduction to Service Orientation MIS 181.9: Service Oriented Architecture 2 nd Semester,
Service Oriented Architecture Enabling the Agile and Flexible Business of the 21 st Century.
1 Acquisition Automation – Challenges and Pitfalls Breakout Session # E11 Name: Jim Hargrove and Allen Edgar Date: Tuesday, July 31, 2012 Time: 2:30 pm-3:45.
A service Oriented Architecture & Web Service Technology.
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
Service Oriented Architecture (SOA) Prof. Wenwen Li School of Geographical Sciences and Urban Planning 5644 Coor Hall
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
CCL.
Enterprise Service Bus
EI Architecture Overview/Current Assessment/Technical Architecture
SOA (Service Oriented Architecture)
Service Oriented Architecture
Intent To provide a framework to manage the process of software salvage and promote loose coupling through message passing. Salvage means recycling significant.
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
Distribution and components
Part 3 Design What does design mean in different fields?
Enterprise Computing Collaboration System Example
7. Service-oriented Architecture (SOA)
Software Testing and Maintenance Designing for Change
موضوع سمینار : نقش مولفه ها در معماری سرویس گرا
Jens Haeusser Director, Strategy IT, UBC
Software Reuse Objectives
Techie Terminology and Benefits for Financial Aid Administrators
Lecture 1: Multi-tier Architecture Overview
Elements of Service-Oriented Architecture
Software Architecture
Design Model Like a Pyramid Component Level Design i n t e r f a c d s
Service Oriented Architecture (SOA)
Integration and API development (With MuleSoft Anypoint Platform)
Service Oriented Architecture + SOAP
An Introduction to Software Architecture
SAMANVITHA RAMAYANAM 18TH FEBRUARY 2010 CPE 691
Introduction to SOA and Web Services
Chapter 6: Architectural Design
Introduction to SOA Part II: SOA in the enterprise
Presentation transcript:

Service-oriented architecture 8 th July 2013

What is a Service? A service is a reusable component that can be used as a building block to form larger, more complex business-application functionality. A service may be as simple as “get me some person data,” or as complex as “process a disbursement.” How the service is implemented, and how a user of the service accesses it, are limited only by the SOA infrastructure choices of the enterprise. From a theory point of view, it really doesn’t matter how a service is implemented. Service-Oriented Architecture (SOA) is an architectural style. Applications built using an SOA style deliver functionality as services that can be used or reused when building applications or integrating within the enterprise or trading partners.

Analogy This model could loosely be compared to a SOA. The people in the house uses a number of different "applications" like radiators, computers, toilets, lamps, under floor heating, bathtubs etc. These applications don't care how the city generates the water, creates the electricity or handles the waste as long as it works. The components of the city are generators, water pumps and sanitation areas. It provides the house with all these needs but it's up to the house to use it in what ever way it sees fit

A real world example(cooks) Let's assume you have 4 cooks. In SOA, you assume they hate each other, so you strive to let them have to talk to each other as little as possible. How do you do that? Well, you will first define the roles and interface -- cook 1 will make salad, cook 2 will make soup, cook 3 will make the steak, etc.. Then you will place the dishes well organized on the table (so these are the interfaces) and say, "Everybody please place your creation into your assigned dishes. Don't care about anybody else.". This way, the four cooks have to talk to each other as little as possible, which is very good in software development -- not necessarily because they hate each other, but for other reasons like physical location, efficiency in making decisions etc.

Revolutionary steps programmers learnt that organizing code into modules made it easy to maintain and reuse This led to the development of large libraries of code that are still used today The next major revolution in software design was object orientation. The implementation details of an object were hidden from the consumers of the object and could be changed as long as the object’s signature remained the same. This led to even greater ease of maintenance and extensibility. where objects could reside on different machines across a network and talk to each other using various remote access protocols. The industry gradually realized that there was a huge potential market for pieces of functionality that could be plugged into software applications and customized for that specific application’s needs. This led to the concept of software components. The latest buzzword in the software industry is ‘Service Orientation’. In this approach, software functionality is defined as a set of services. Service Oriented Architecture (SOA) Explained

SOA is an evolutionary step  for architecture

Motivation Applicatio n Centric Goal - Service Centric Service Centric

Before SOA – After SOA source:IBM

SOA is acronym for Service Oriented Architecture. SOA is designing and writing software applications in such a way that distinct software modules can be integrated seamlessly with high degree of re- usability. Most of the people restrict SOA as writing client/server software-web- services. But it is too small context of SOA. SOA is much larger than that and over the past few years web-services have been primary medium of communication which is probably the reason why people think of SOA as web- services in general restricting the boundaries and meaning of SOA. You can think of writing a database-access module which is so independent that it can work on its own without any dependencies. This module can expose classes which can be used by any host-software that needs database access. There's no start-up configuration in host-application. Whatever is needed or required is communicated through classes exposes by database- access module. We can call these classes as services and consider the module as service-enabled.

What is Service Architecture? A collection of services classified into types arranged into layers Governed by architectural patterns and policies services identification granularity dependency type source:TietoEnator AB, Kurts Bilder

Benefits of Service Oriented Architecture (SOA): 1. Platform Independence – 2. Focused Developer Roles – 3. Location Transparency – 4.Code Reuse _ 5. Greater Testability 6. Parallel Development – 7. Better scalability – 8. Higher availability –.

What is an Enterprise Service Bus An enterprise service bus is an infrastructure used for building compound applications is the glue that holds the compound application together is an emerging style for integrating enterprise applications in an implementation-independent fashion can be thought of as an abstraction layer on top of an Enterprise Messaging System is an infrastructure used for building compound applications is the glue that holds the compound application together is an emerging style for integrating enterprise applications in an implementation-independent fashion can be thought of as an abstraction layer on top of an Enterprise Messaging System

Characteristics of ESB Key Characteristics of an ESB Streamlines development Supports multiple binding strategies Performs data transformation Intelligent routing Real time monitoring Exception handling Service security

SOA Principles Standardized Service Contracts Loose Coupling Abstraction Reusability Autonomy Statelessness Discoverability Composability

SOA Depends on who you are! Business owner: is a solution to increase your incomes and business. Enterprise architect: is a way to draw nice and clean piece of software on a blank canvas. Architect: is the solution to design loosely coupled services over an integration platform, to just plug services into outlets. Developer: is a programming paradigm where a service is in the center of the design and the code.

SOA Depends on who you are! Business owner: is a solution to increase your incomes and business. Enterprise architect: is a way to draw nice and clean piece of software on a blank canvas. Architect: is the solution to design loosely coupled services over an integration platform, to just plug services into outlets. Developer: is a programming paradigm where a service is in the center of the design and the code.

SOA Depends on who you are! Business owner: is a solution to increase your incomes and business. Enterprise architect: is a way to draw nice and clean piece of software on a blank canvas. Architect: is the solution to design loosely coupled services over an integration platform, to just plug services into outlets. Developer: is a programming paradigm where a service is in the center of the design and the code.