To Understand and get started with Service Oriented Architecture

1. SOA
DURGASURESH KAGITHA

3. What Is SOA

4. Service Oriented Design

5. Orientation & Integration

6. Ingredients
 Data
 Business Logic
 Presentation
 Validations
Architecture
 Design to layout your software applications
 Structure needed to bind software elements, their
relations and their properties

7. Architecture history
2-Tier70’s
80’s
2-Tier
Client/server
Late 90’s
3-Tier
easy scalability
scalability maintenance
scalability
maintenance
complexity

8. Architecture history ..
Early 00’s
ERP software
Adapter based
Integration
Point -to- Point
Integration
Not Scalable
00’s - ESB
Middleware
Single Point
Integration
Isolation of
Business logic
Interoperability
& Reusability
Late 00’s
SOA
Isolation of
Business Logic &
Orchestration
Reusable components
as services
ESB’s capable of
exposing services
n-Tier

9. SOA
Software Design
Architectural Approach to develop Information
systems
Layout on Software providing application
functionality as Services to other applications
SOA tends to embody a "don't replace, embrace"
systems philosophy
SOA is a way to implement Distributed Computing

13. Why SOA ??

14. Evolution….

16. It’s all about the message !

17. Services
 Self Contained Business Functionality
 Communicate using Messages
 Discoverable
 Loosely Coupled
 Interoperable
 Orchestrated

18. Self contained / Interdependent

19. Interoperable

20. Orchestrate
 Juggling image

21. Check this out …
 https://www.youtube.com/watch?v=A3_QlYJRVvk
 https://www.youtube.com/watch?v=L1tM0tMJdzY
 https://www.youtube.com/watch?v=IIWVIa6QhkM

22. 22
As a distributed computing architecture, Web Services
are the most important implementation for SOA.
SOA Model is Web Services Concept Architecture.
SOA Model

23. 23
Concept in SOA Model
Role
Services Provider
Services Requestor
Services Registry
Operation
Publish
Find
Bind
Key Component
Services
Services Description

24. Messages travel in
no man’s land!

25. Operation Types
The request-response type is the most common
operation type, but WSDL defines four types:
One-way: The operation can receive a message
but will not return a response
Request-response: The operation can receive a
request and will return a response
Solicit-response: The operation can send a
request and will wait for a response
Notification: The operation can send a message
but will not wait for a response

26. Where slide ??

27. Applications
 Banking
 Credit Check
 Lookup service –Postcode / Zip code
 Payment Processing
 Weather Reports
 Order Processing
 Many more…

28. How to find you …

29. 29
Ingredients of WSDL
OperationPort Type
MessageBinding
Port Services
Supports
Input & Output
Provides
How to encode
Formats & Protocols
Implements
Interface
Access
specification
Endpoints

30. ISOLATE

31.  Pros
 Discoverability
 Composability
 Formal contract
 Loose coupling
 Reusability
 Synchronous and asynchronous messaging
 Cons
Still Complex
Maintenance of Metadata (information on how services
communicate)
Limited number of Test Tools in SOA space
Security concerns in a highly Distributed systems
Benefits & Limitations

32. What next ….

33. Big Data as a service….

34. SOA & BIG DATA