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 • 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
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
Focus Areas Critical to EDA Success Organization Corporate Competency development/evolutionSoftware/Hardware Methodology/Practices Consistent approachEnterprise EDA to EDA engineeringInfrastructure Planning Process & and management Roadmap to guide you Business Alignment RTE Strategy Alignment
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 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
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
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 aboutBPM 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 OfferingsEDA Datasheets and • Planning & assessment services tools Other Tools MDM • Datasheets • ROI Tools • Training/Presentation Material
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.
SummaryEvent 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
The preceding is intended to outline our generalproduct direction. It is intended for informationpurposes only, and may not be incorporated into anycontract. It is not a commitment to deliver anymaterial, code, or functionality, and should not berelied upon in making purchasing decisions.The development, release, and timing of anyfeatures or functionality described for Oracle’sproducts remains at the sole discretion of Oracle.