EI - SOA Presentation (Zuhair, Hairs, Saad)

8/3/2019 EI - SOA Presentation (Zuhair, Hairs, Saad)

1/14

BENEFITS OF SERVICE ORIENTED

ARCHITECTURE


2/14

y Stronger connections with customers &

suppliers.

yEnhanced business decision making.

y

Greater employee productivity.


3/14

SOA Solution Approach

SOA can be summarized as a three step approach.

1. Expose Phase Existing IT services are made

available.

2. Compose Phase Exposed services need to bepulled together or composed into larger business

processes or workflows.

3. Consume Phase Applications are developedwhich consume the underlying services &

processes.


4/14

COMMON MISUNDERSTANDINGS /

PITFALLS

y SOA solution requires a complete overhaul of existing

technologies.

y SOA implementation is a costly and complex proposition.

ySOA technology is only for large Fortune 1000 companies.

y SOA is a product.


5/14

y SOA is an end rather than means to an end.

y Trying to built SOA solution rather than solution to a specific

problem.

y Trying to solve multiple problems at once.

y Taking either a Top down or a Bottom up approach.


6/14

SOA Reference Model

What is a Reference Model?

abstract framework for understanding significant relationships among the entities of some environment

develops specific reference or concrete architecture using consistent standards supporting the environment

consist of a minimal set of unifying concept, axioms and relationships within a particular problem domain

Purpose of a Reference Model

To provide a common conceptual framework that can be used consistently for an implementation, particularly used in

modeling a specific solution

Example

In the context of Reference Model for a House

Concept of Eating area, Hygiene area and Sleeping area are important in understanding what goes into a house

There will be relationships b/w these concepts and constraints on how they are implemented

For example, there may be physical seperation b/w Eating area and Hygiene area, etc


7/14

An Abstract SOA Reference Model

SOAs are like snowflakes no two are alike.

- David Linthicum, Consultant

Very simply defined

A loosely-coupled architecture designed to meet the business needs of the organization

Not all service-oriented efforts have been

successful

When using bottom-up approach, SOA projects experience limited success. Because

Developers are unfamiliar with the needs of the organization

Building SOA for the sake of SOA is a project without principles and guidance, resulting in chaos

When using top-down approach, SOA projects experience limited success. Because

Requires enormous time

when project is complete, the solution no longer maps to business needs

There is another approach which is called a middle out approach which combines both top-down and bottom-up methodologies


8/14

SOA middle out approach

In this approach,

SOA efforts are driven by strategic vision and business need

SOA projects are designed to deliver on business goals, one business need at a time

The middle out approach basically advocates three abstract capability layers exposed within an SOA, these three layers are:

An illustration of these categories appear below:

Expose Compose Consume


9/14

Expose

Basically means, Identify legacy apps, products and expose them as services.

Focuses on how existing IT investments are exposed as a set of broad, standard-based services

Making the IT investment available to a broader set of consumers Concerns with how the services are implemented

Can also be referred to as Service Implementation Architecture

Compose

Compose the various apps. in the organization into orchestrations using workflow, etc.

combination of services into more complex, cross-functional business processes or workflows

Allows the organization to adopt new business processes, tune processes for greater efficiency, or improve service levels for

customers and partners

Can also be referred to as Service Integration Architecture

ConsumeCreate disparate clients to consume these services

Delivering new application that enable increased productivity and enhanced insight into business performance

Users may consume "composed" services through broad number of outlets, i.e web portals, rich clients, mobile devices or

OBAs

Can Also be referred to as Service Oriented Application Architecture


10/14

Recurring Architectural Capabilities

We know that Expose / Compose / Consume portion of the model can be thought of as independent architectural initiatives

and they are designed to be independent of each other, they share a set of five common capabilities

Messaging and

Services

Workflow and

Process

Data User

Interaction

Identity and

Access

Focus on how

messaging is

accomplished between

senders and receivers.

Spread across multiple

layers of an integration

architecture

Must be dynamic,

evolve with the

organization and

adaptable

Data management,

the Lynchpin to

success in many

integration

architecture.

Entity aggregation,

master data

management, making

data useful via

analytics and mining

An integrated User

Experience spanning

smart clients, rich

clients, lightweightWeb

applications, and mobile

devices enables service

consumption by the

broadest possible

audience.

Customers require the

ability to manage the

identity lifecycle

Integrated Single

Sign-On(SSO)

Access Management

Directory Services

Federated trust across

heterogeneous systems


11/14

Microsoft RealWorld SOA


12/14

y Consequences due to lack of integration among IT assets?

y What is SOA?

y Microsofts middle out approach

y How SOA works?

Background


13/14

y Web Services

y SaaS and SOA

y BPM and SOA

y SOA benefits and challenges

SOA


14/14

y The Dos and Donts

y Initiating SOA in your enterprise

Conclusion

EI - SOA Presentation (Zuhair, Hairs, Saad)

Documents

Transcript of EI - SOA Presentation (Zuhair, Hairs, Saad)