Todd PapaioannouVP Architecture and

Emerging Technologies

Service Oriented Architectures

1

Whatare Service Oriented

Architectures?

2

‘Fraid Not!3

SOAP (Simple Object Access Protocol)

REST (Representational State Transfer)

XML-RPC

Mashups

4

Whyuse build SOAs?

5

Decoupled Architectures

Platform agnostic

Service/Contract driven model

Extensible

6

Whenshould you use SOAs?

7

Experts & Strategists

Knowledge Workers

Front Line Users

Decisions per Minute Many Few

Co

mp

lexit

y

High

Low

DecisionAutomation

DecisionSupport

Human Intellect

Yes

No

8

Issues

9

Service Explosion

SOA Governance

Contract life cycle

Complexity

Interoperability

10

Howdoes this relate to

Teradata?

11

Active Data Warehouse from Teradata

Enterprise Service Bus

Transaction Systems

Service Brokers

Integration Adapters

BPM/ Workflow

Business Rules

Data Integration

Active Events

Active Load

Active Access

Expose Services

12

Howdo I succeed with

SOA?

13

Think!14

You could build this

Good Architecture15

Or, you could build this

Bad Architecture16

Summary

17

SOA is a great technology if

done right

18

You can drive real time value from your DW

19

You can deliver SaaS, or your own

cloud services

20

Questions?

21

Roll the Photo Credits

http://flickr.com/photos/dcdead/2363635002/

http://www.flickr.com/photos/xeophin/2181342710/

http://www.flickr.com/photos/edtarwinski/454682301

http://www.flickr.com/photos/liberato/171610084/

http://flickr.com/photos/davelau/1227552621

22