• Save
SOA, SOA 2.0 and EDA Defined and Illustrated
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

SOA, SOA 2.0 and EDA Defined and Illustrated

  • 5,997 views
Uploaded on

SOA, “SOA 2.0” and EDA Defined and Illustrated with CEP/EP Included. August 31, 2006 Version v 2.4, Tim Bass, CISSP, Principal Global Architect, Director, TIBCO Software Inc.

SOA, “SOA 2.0” and EDA Defined and Illustrated with CEP/EP Included. August 31, 2006 Version v 2.4, Tim Bass, CISSP, Principal Global Architect, Director, TIBCO Software Inc.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
5,997
On Slideshare
5,962
From Embeds
35
Number of Embeds
3

Actions

Shares
Downloads
0
Comments
0
Likes
11

Embeds 35

http://www.thecepblog.com 17
http://www.slideshare.net 17
http://static.slideshare.net 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SOA, “SOA 2.0” and EDA Defined and Illustrated with CEP/EP Included September 12, 2006 Draft v 2.4 Tim Bass, CISSP Principal Global Architect, Director TIBCO Software Inc.
  • 2. Preface
    • This briefing was prepared in response to some of the new marketing hype around “Advanced SOA” and “SOA 2.0”
    • It is a dynamic, work in progress.
    • Please feel free to send comments and suggestions.
  • 3. Key SOA / SOA 2.0 / EDA Takeways
    • SOA, SOA 2.0 and EDA are all “Event-Driven”
    • Gartner’s principal analysts now (re)define SOA as follows:
      • SOA 2.0 = distributed computing services (based on interfaces)
      • In this “new definition” SOA is a “Superclass” that contains EDA.
    • Before “SOA Redefined” - EDA could have been considered, technically, a “Superclass” of “traditional” SOA because:
      • EDA was generally unmanaged message interaction between strongly decoupled or very loosely coupled applications.
      • SOA was “traditionally” managed or “orchestrated” interaction between loosely coupled applications, modeled as services
      • “ Newly Defined SOA” is simply, “distributed computing services with interface definitions”
      • “ Traditional SOA” was more “complex” than EDA (required orchestration, etc.)
      • “ Traditional SOA” required more scheduling overhead that EDA
      • “ Traditional SOA” was less “ad hoc” and more tightly coupled than EDA
    • Either way, both SOA and EDA are required for enterprise optimization
    • Either way, SOA and EDA are complimentary architectures
  • 4. SOA (1.0) Defined**
    • SOA is a application architecture in which all functions, or services, are defined using a description language and have invokable interfaces that are called to perform business processes.
    • Each interaction is independent of each and every other interaction and the interconnect protocols of the communicating devices (i.e., the infrastructure components that determine the communication system do not affect the interfaces).
    • Because interfaces are platform-independent, a client from any device using any operating system in any language can use the service.
    • http://www.webopedia.com/TERM/S/Service_Oriented_Architecture.html
    **Please Note: Gartner Principal Analysts now say that SOA 2.0 ~ “distributed computing services w/interfaces”
  • 5. EDA Defined
    • EDA is an enterprise software infrastructure model in which events trigger the real-time exchange of messages between independent software applications.
    • EDA relies on an event-processing agent that detects events across an enterprise and, using a push approach, notifies all of the other software applications that need to be notified of the change in data, all at the same time.
    • For example: the e-commerce Web site of an enterprise receives an order for a product, completing a business event. An event agent detects this transaction and simultaneously notifies all other applications in the enterprise that need to know about the order, which can include such aspects as an inventory database, accounts receivable software, customer service applications, marketing and advertising monitors, and shipping software.
    • http://www.webopedia.com/TERM/E/EDA.html
  • 6. EDA Visualized Asynchronous, Strongly Decoupled, Not Orchestrated A A A A A A A A A A Message Message Message Message Message Message Message Message
  • 7. “Traditional SOA” + EDA Visualized Synchronous & Asynchronous, Loosely Coupled & Strongly Decoupled, Managed, Orchestrated, Not Orchestrated, Consumer-Driven, Producer-Driven Orchestrated Messaging (SOA) Orchestrated Messaging (SOA) Not Orchestrated Messaging (EDA) Note: Request/Reply Implied in “ Orchestrated Messaging” A A A A A A A A A A Message Message Message Message Message Message Message Message
  • 8. “ Traditional SOA” – EDA: Table of Characteristics Draft Comparison – Under Construction Asynchronous Event Triggers Synchronous Service Invocation Application Interaction Flow Control Faster Sense/Respond Service Component Reuse Primary Technical Goal Reduced Costs and Increased Visibility Reduce Costs and Time-to-Market Primary Business Goal One-to-One, One-to-Many, Many-to-Many One-to-One Process Communication Models Publish/Subscribe Orchestration Process Management Producer Consumer Process Trigger No Scheduler Scheduler Required Process Coordination Strongly Decoupled Loosely Coupled Application Interaction EDA SOA Architectural Characteristic
  • 9. “ Newly Defined SOA” – EDA: Table of Characteristics Draft Comparison – Under Construction Asynchronous Event Triggers Synchronous & Asynchronous Service Invocation Application Interaction Flow Control Faster Sense/Respond Distributed Computing Primary Technical Goal Reduced Costs and Increased Visibility Reduced Costs, Time-to-Market, and Increased Visibility Primary Business Goal One-to-One, One-to-Many, Many-to-Many One-to-One, One-to-Many, Many-to-Many Process Communication Models Publish/Subscribe Orchestration & Pub/Sub Process Management Producer Consumer or Producer Process Trigger No Scheduler Scheduled & Unscheduled Process Coordination Strongly Decoupled Decoupled, Loosely Coupled Application Interaction EDA SOA 2.0 Architectural Characteristic
  • 10. FYI: Event Processing (EP) and CEP Visualized A A RE A A A A A A A Messages Messages Messages Messages Messages Message Messages Messages Many-to-One Asynchronous Events Processing with Rules Engine (RE)
  • 11. SOA + EDA + CEP Visualized (with Rules Engine) A A A A A A A RE A A Message Message Message Message Message Messages Messages Message Synchronous & Asynchronous, Loosely Coupled & Decoupled, Managed, Orchestrated, Not Orchestrated, Consumer-Driven, Producer-Driven Orchestrated Messaging (“Traditional” SOA) Orchestrated Messaging (“Traditional” SOA) Not Orchestrated Messaging (EDA) Messages Note: Request/Reply Implied in “ Orchestrated Messaging”
  • 12. Key SOA / SOA 2.0 / EDA Takeways
    • SOA, SOA 2.0 and EDA are all “Event-Driven”
    • Gartner’s principal analysts now (re)define SOA as follows:
      • SOA 2.0 = distributed computing services (based on interfaces)
      • In this “new definition” SOA is a “Superclass” that contains EDA.
    • Before “SOA Redefined” - EDA could have been considered, technically, a “Superclass” of “traditional” SOA because:
      • EDA was generally unmanaged message interaction between strongly decoupled or very loosely coupled applications.
      • SOA was “traditionally” managed or “orchestrated” interaction between loosely coupled applications, modeled as services
      • “ Newly Defined SOA” is simply, “distributed computing services with interface definitions”
      • “ Traditional SOA” was more “complex” than EDA (required orchestration, etc.)
      • “ Traditional SOA” required more scheduling overhead that EDA
      • “ Traditional SOA” was less “ad hoc” and more tightly coupled than EDA
    • Either way, both SOA and EDA are required for enterprise optimization
    • Either way, SOA and EDA are complimentary architectures
  • 13. Key Takeways: SOA – EDA – CEP/EP
    • SOA, EDA and CEP/EP are all “Event-Driven” architectures
    • CEP/EP is a “Subclass” of EDA (and now SOA 2.0) because:
      • CEP/EP-style “processing” occurs within an EDA
      • CEP/EP is a special subclass of EDA where applications receive many events from many distributed events sources
    • CEP/EP requires powerful, scaleable rules processing
    • CEP/EP may require state management
    • CEP/EP can address more complex classes of business problems that SOA or EDA without CEP/EP
    • CEP is a decoupled architecture like it’s “Superclass” EDA
    • SOA, EDA and CEP/EP are required for enterprise optimization
    • SOA, EDA and CEP/EP are complimentary architectures
  • 14. Work in Progress Please Send Comments: Tim Bass, CISSP Principal Global Architect [email_address] Complex Event Processing at TIBCO
  • 15. End Notes:
    • Messaging technologies, like RV, JMS/EMS or ESB, etc. are “assumed” in the illustrations by the words “messages”.
    • Gartner and others have/are redefined/redefining SOA as “SOA 2.0” and “Advanced SOA” to encompass the entire domain of distributed computing services “based on service interfaces”.
    • There are a number of “critics” to this “new definition of SOA” and the “jury is still out” on where all this new “SOA marketing” will lead.