This document discusses moving from a traditional SOA approach to an event-driven SOA 2.0 approach. It argues that the current SOA model is too passive and static, relying only on human improvements. A new EDO (Event-Driven Orchestration) and ESM (Event Services Monitoring) approach is proposed to make services more responsive to events. This would allow processes and services to react in real-time to events and make immediate improvements, rather than following lengthy human-driven improvement cycles. EDO specifically aims to use events to dynamically orchestrate services, rather than relying only on static process timelines.

2. “When SOA Meets the Clouds”
A SOA perspective from trenches
Edgar A Silva
JBoss Brazil

3. In the Real World...
Events driven billions of people
Different people may react differently against
some events
Examples:
Simple lights in semaphores
Raising a hand on front of some taxi
A simple smile..

4. So Why...
We have a complete passive model when we
are designing a Service Oriented
Architecture?
Many events happens into a business
organization and Services can react on just
one single way?

5. Some actual SOA drawbacks
Fault of Services Resilience
Processes are statics and depending
dramatically of improvements made just by
humans
Passiveness Services

6. Time to change...
Time to identify new patterns for a SOA 2.0
approach:
EDO- Event-driven Orchestration
ESM – Event Services Monitoring

7. Conceptual Foundation
CEP/ESP – Complex Event Processing
JEE6 Profile Services
OSGI
SOA 2.0 = SOA1.0+Events+Responsiveness

8. EDO-Event-Driven Orchestration
Actual Orchestration Techniques:
Many languages, few interaction
Our long frustration over BPEL for years
Many standards, few exchange
Why SCA when we already had JBI?
Even with all those shortcomings do you
really expect that your orchestration could
works fine?

9. EDO-Event-Driven Orchestration
Big mistakes over Processes
BPM and its big confusing on the “M”
Management
Basically an Engine
Modeling
A Designing Tool
Measurement
A Monitoring and Metrics tool
Poor reality: No options counting with
everything in just one Tool/Product

10. EDO-Event-Driven Orchestration
Processes
Why do you need BAM?
As one of the answer you can tell: “To answer where
are the weaknesses into my processes”
How fast could you react against some
weakness into your process?
a) Stop, Planning, Wait others humans interactions,
Test and Deploy...
b) Measure and Deploy...

11. EDO-Event-Driven Orchestration
Processes X Measure
Measure
Shall be an Event
Which are fired in a time-window
According some circumstances a process can react
productively, promoting changes in real-time in order
to obtain a better:
a) Performance
b) Results
c) Reducing drastically time and costs for the changes

12. EDO-Event-Driven Orchestration
Services Orchestration based in Process
Service 1
Service 2
Service 3
Time line for signal an orchestration process
External System Action
JMS Message
Human Interaction
Just these action on this time-line
can operate the services

13. EDO-Event-Driven Orchestration
Services Orchestration based in Events
Service 1
Service 2
Service 3
Time line for signal an orchestration process
Events can be set of actions and can influence the process
in any time and in real-time

14. EDO-Event-Driven Orchestration
Services Orchestration based in Events
Service 1
Service 2
Service 3
Time line for signal an orchestration process
Events can be set of actions and can influence the process
in any time and in real-time
Service 3
A Newer Version

15. EDO-Event-Driven Orchestration
Services Orchestration based in Events
Events Services Monitoring – A New way to
see BAM
Service 1
Service 2
Service 3
Time line for signal an orchestration process
Events can be set of actions and can influence the process
in any time and in real-time
Service 3
A Newer Version

16. Questions