The document discusses Oracle's approach to event driven architecture (EDA). It provides an overview of EDA and the business drivers for adopting an EDA approach. It then details Oracle's EDA reference architecture, including the conceptual view, logical view, product mapping, and deployment view. The reference architecture provides guidance on developing EDA solutions using Oracle products.

2. <Insert Picture Here>
Oracle’s Approach to Event Driven Architecture
Enabling Real-Time Enterprise (RTE) Transformation
Anbu Krishnaswamy
Enterprise Architect
Oracle Corporation

3. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

4. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

5. Event Driven Architecture - Defined
EDA is a style of architecture that enables
Real-Time Enterprise (RTE)
transformation through production,
detection, processing, and consumption of
business events to identify and react to
business opportunities, threats and
anomalies.

6. Real-Time Enterprise
“The Real-Time Enterprise (RTE) is an
enterprise that competes by using up-to-
date information to progressively remove
delays to the management and execution
of its critical business processes.” - Gartner

7. EDA Drivers
• Revenue Growth Drivers
• Shorten sales and delivery cycles • Agility and TTM Drivers
• Real-time capabilities to gain • Monitor, sense, and react to market
competitive advantage changes
• Enhance customer experience -> • Faster product and service rollout
improved customer loyalty • Situation Awareness - Real-time
• Identify and execute up-sell/cross- visibility for business decisions
sell opportunities
• Technology Drivers
• Cost Reduction Drivers • Loosely Coupled Architecture
• Reduce cost by JIT operations • High volume, low latency
• Boost profitability by faster order processing
processing and fulfillment • Process and Service interaction
• Eliminate waste through a lean • Partner integration
approach
• Real-time monitoring
• Mergers and Acquisitions
• Pattern Matching and Analysis

8. Application of EDA
Distributed order orchestration
Asset management
Need to support one or more of:
Algorithmic trading • High volume
Financial Services
• Continuous streaming
Transportation &
Logistics
• Sub-millisecond& latency
Telecommunications
Services
• Disparate sources
Manufacturing
Shop floor
• Time window processing
Insurance monitoring
Public Sector & Military
• Intrusion detection systems • Complex pattern matching
• Military asset allocation
Reponses to calamities –
earthquake, flooding

9. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

10. Focus Areas Critical to EDA Success
Organization
Corporate Competency
development/evolution
Software/Hardware Methodology/Practices
Consistent approach
Enterprise EDA to EDA engineering
Infrastructure Planning Process & and management
Roadmap to guide
you
Business Alignment
RTE Strategy
Alignment

11. EDA Enterprise Technology Strategy

12. EDA Maturity Model
Capability Domains Measurement Model
• Eight capability domains – comprehensive coverage
• Domain – A collection of related capabilities
• Model measures maturity and adoption levels

13. EDA Maturity Model Capabilities

14. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

15. EDA Strategy & Planning – Basics
• Plan Strategically
• EDA Reference Architecture
• EDA Engineering
• Enterprise EDA Modeling
• Organization and Governance
• Act Tactically
• Take a pragmatic approach
• Address only the immediate
concerns in each iteration
• Four step process
• Understand current state
• Define future vision
• Identify gaps “Leverages Oracle’s EDA Maturity Model”
• Develop roadmap

16. EDA Roadmap Planning
• Plan and manage holistically
– multiple dimensions, multiple
phases and time periods
• Remedy problem areas –
Use EDA Domain Capability
Heat Maps to identify problem
areas and inhibitors to EDA
EDA Planning Horizon
adoption
• Close Gap – Use EDA
Domain detailed strategies for
closing the “as-is” and “to-be”
gap.
• Improve - You can’t improve
what you can’t measure
Maturity Over Time

17. EDA Project Identification Analysis

18. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

19. IT Strategies from Oracle

20. Enterprise Technology Strategy Contents
Oracle Perspective
• Extends core ORA documentation and
provides an architecture viewpoint from
SOA a unique technology perspective
Practitioner Guides
Practitioner
EPM • Offer detailed information about
BPM Guides
delivering solutions based on that
/ BI
Service Maturity particular technology strategy
Offerings Model
Maturity Model
ORA
Perspective • Measure maturity and adoption of a
technology strategy using a universal
Training/
Presentation …
model and toolset
Material
… Service Offerings
EDA Datasheets
and • Planning & assessment services
tools
Other Tools
MDM • Datasheets
• ROI Tools
• Training/Presentation Material

21. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

22. Event Classifications
Volume
Stream Transactional
Events Events
Significance
Ordinary Notable
Events Events
In-memory Reliable
Messaging Messaging

23. Processing Domains
Volume
Event Complex
Stream Event
Processing Processing
Relativity
Simple Complex
Event Event
Processing Processing

24. Event Lifecycle/ State Change
Generate
React Capture
Monitor
Event
Distribute Process
Cache

25. EDA Conceptual View

26. EDA Capabilities

27. EDA Architecture Sample Principles
• Event driven systems must be loosely coupled.
• Event driven systems must be standards based.
• Business events must be discoverable.
• EDA must be designed to support interoperability and must
complement existing technologies.
• Events must be captured and processed at the most granular
level.
• EDA must focus on supporting and handling business events.
• The architecture must be modular and must support extensibility.
• Event Driven Architecture must enable low latency processing
and be able to support processing of high volume of events.
• Events that are sensitive must only be made available to the
appropriate systems/users.

28. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

29. EDA High Level Logical View

30. EDA Detailed Logical View

31. Event Processing Networks (EPN)
Rule
Processo Consumer
r
Listener
Producer 1 Adapter 1
Processor
Rule
Producer 2 Adapter 2
Processor
Rule
Processor
Listener
Producer n Adapter n
Cache Processor
Rule Consumer
Event
Producers Adapters Event
Event Processors
Consumers

32. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

33. EDA Oracle Product Mapping

34. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

35. EDA Sample Deployment

36. EDA Deployment View (HA & Scalability)
Scalable Server Group1
Primary Server
OS1
Processor1 Adapter
IS1 Secondary Server
[OS1]
Processor1 Adapter
Queue
OS1+OS2
IS1+IS2
Inbound Channel Router Outbound Channel
Scalable Server Group2
Primary Server
OS2
IS2 Processor1 Adapter
Secondary Server
[OS2]
Processor1 Adapter
IS => Input Stream
Queue
OS => Output Stream
[xx] => Backup Stream

37. Presentation Agenda
• EDA Introduction and Drivers <Insert Picture Here>
• EDA Roadmap Creation
• Strategy And Planning
• EDA Reference Architecture
• ITSO and Oracle Reference Architecture
• Conceptual View
• Logical View
• Product Mapping View
• Deployment View
• Summary

38. Summary
Event Driven Architecture (EDA) is an enabler of Real-Time Enterprise
(RTE) and provides competitive advantage through revenue growth, cost
savings, agility, and faster TTM benefits.
Oracle’s Approach to EDA helps the customers accelerate their EDA
adoption through a systematic and comprehensive approach.
Oracle Reference Architecture (ORA) is a single, unified reference
architecture across the middleware space that offers insight and
guidance on many aspects of computing that pertain to solution
development in a modern computing environment.
ORA EDA Reference Architecture drives business value by accelerating
EDA solution delivery and improving quality of EDA solutions
For more information on Oracle Reference Architecture (ORA), please
visit http://www.oracle.com/goto/itstrategies

39. The preceding is intended to outline our general
product direction. It is intended for information
purposes only, and may not be incorporated into any
contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decisions.
The development, release, and timing of any
features or functionality described for Oracle’s
products remains at the sole discretion of Oracle.