<Insert Picture Here>

Oracle’s Approach to Event Driven Architecture

Enabling Real-Time Enterprise (RTE) Transformation

Anbu Krishnaswamy

Enterprise Architect

Oracle Corporation

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

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.

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

EDA Drivers

• Revenue Growth Drivers

• Shorten sales and delivery cycles

• Real-time capabilities to gain

competitive advantage

• Enhance customer experience ->

improved customer loyalty

• Identify and execute up-sell/cross-

sell opportunities

• Cost Reduction Drivers

• Reduce cost by JIT operations

• Boost profitability by faster order

processing and fulfillment

• Eliminate waste through a lean

approach

• Mergers and Acquisitions

• Agility and TTM Drivers

• Monitor, sense, and react to market

changes

• Faster product and service rollout

• Situation Awareness - Real-time

visibility for business decisions

• Technology Drivers

• Loosely Coupled Architecture

• High volume, low latency

processing

• Process and Service interaction

• Partner integration

• Real-time monitoring

• Pattern Matching and Analysis

Application of EDA

Financial Services

Transportation & Logistics

Public Sector & Military

Manufacturing

Insurance

Telecommunications & Services

Algorithmic trading

Asset management

Distributed order orchestration

Shop floor

monitoring

Reponses to calamities –

earthquake, flooding

• Intrusion detection systems

• Military asset allocation

Need to support one or more of:

• High volume

• Continuous streaming

• Sub-millisecond latency

• Disparate sources

• Time window processing

• Complex pattern matching

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

Focus Areas Critical to EDA Success

Planning Process &

Roadmap to guide

you

Enterprise EDA

Infrastructure

Software/Hardware

Consistent approach

to EDA engineering

and management

Methodology/Practices

Corporate Competency

development/evolution

Organization

RTE Strategy

Alignment

Business Alignment

EDA Enterprise Technology Strategy

EDA Maturity Model

Capability Domains Measurement Model

• Eight capability domains – comprehensive coverage

• Domain – A collection of related capabilities

• Model measures maturity and adoption levels

EDA Maturity Model Capabilities

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

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

• Develop roadmap

“Leverages Oracle’s EDA Maturity Model”

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

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

EDA Planning Horizon

Maturity Over Time

EDA Project Identification Analysis

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

IT Strategies from Oracle

Enterprise Technology Strategy Contents

EDA

BPM

SOA

EPM

/ BI

…

MDM

Practitioner

Guides

Training/

Presentation

Material

Service

Offerings

Maturity

Model

…

Datasheets

and

tools

ORA

Perspective

• Extends core ORA documentation and

provides an architecture viewpoint from

a unique technology perspective

Oracle Perspective

• Offer detailed information about

delivering solutions based on that

particular technology strategy

Practitioner Guides

• Measure maturity and adoption of a

technology strategy using a universal

model and toolset

Maturity Model

• Planning & assessment services

Service Offerings

• Datasheets

• ROI Tools

• Training/Presentation Material

Other Tools

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

Event Classifications

Stream Events

Transactional Events

Ordinary Events

Notable Events

Significance

Volume

Reliable Messaging

In-memory Messaging

Processing Domains

Event Stream

Processing

Complex Event

Processing

Simple Event

Processing

Complex Event

Processing

Relativity

Volume

Event Lifecycle/ State Change

Event

Generate

Capture

Process

Cache

Distribute

React

Monitor

EDA Conceptual View

EDA Capabilities

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.

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

EDA High Level Logical View

EDA Detailed Logical View

Event Processing Networks (EPN)

Processor

Lis

ten

er

RuleProcessor

RuleProcesso

r

RuleProcessor

RuleProcessor

Lis

ten

er

Producer 1

Producer 2

Producer n

Event Producers

Adapter 1

Adapter 2

Adapter n

Adapters

Cache

Event Consumers

Event Processors

Consumer

Consumer

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

EDA Oracle Product Mapping

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

EDA Sample Deployment

EDA Deployment View (HA & Scalability)

Processor1

Router

Primary Server

Secondary Server

Adapter

Outbound Channel

Queue

Scalable Server Group1

Processor1 Adapter

Processor1

Primary Server

Secondary Server

Adapter

Queue

Scalable Server Group2

Processor1 Adapter

IS1

IS2

IS1+IS2

Inbound Channel

OS1

[OS1]

OS2

[OS2]

OS1+OS2

IS => Input Stream

OS => Output Stream

[xx] => Backup Stream

<Insert Picture Here>

Presentation Agenda

• EDA Introduction and Drivers

• EDA Roadmap Creation

• Strategy And Planning

• EDA Reference Architecture

• ITSO and Oracle Reference Architecture

• Conceptual View

• Logical View

• Product Mapping View

• Deployment View

• Summary

Summary

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.

For more information on Oracle Reference Architecture (ORA), please

visit http://www.oracle.com/goto/itstrategies

ORA EDA Reference Architecture drives business value by accelerating

EDA solution delivery and improving quality of EDA solutions

Oracle’s Approach to EDA helps the customers accelerate their EDA

adoption through a systematic and comprehensive approach.

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.

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.