Presented By : Chandra Vardhan(11030241006) Mamta Kunawat(11030241017) Shashank Vishwakarma(11030241029) Akshay Upadhyay(11030241042) Anirudha Ingle(11030241210)

Contents
y Introduction y Definition y How EDA Works y EDA Diagram y Event Processing styles y Advantages y Challenges y Conclusions

Introduction
 An event is a notable thing that happens inside or outside your
business.
y Example of events business terms are such as a bank

transaction, stock trade, customer order, address change, shipment delivery or buying a house.
y Computers can t manipulate events because they are

abstractions; so an application system must create an event object an electronic signal or report of the event.

y Example: The fact that Smith withdrew Rs 100 from his bank

account at 10 AM is an event. The computer record associated the withdrawal transaction(XML) is the event object.
y What does an Event Contain ?

Each event occurrence has an event header and event body. The event header contains elements describing the event occurrence and the event body describes what happened.
y Example: For the low inventory threshold event : The event

header contains elements ID, event type, name, time stamp, the event body would contain product identifier, product
description, and the point in time inventory and threshold levels

Definition
y Event driven architecture (EDA) is a software architecture pattern

that facilitates the production, monitoring, and reaction of events

y Event driven architecture gives decision makers the ability to

receive and work with business data in real time and to improve the rate of response to incoming data.
y Building applications and systems around an event-driven

architecture allows these applications and systems to be constructed in a manner that facilitates more responsiveness, because event-driven systems are, by design, more normalized to unpredictable and asynchronous environments.

How EDA Works:

y When a thing happens inside or outside the business, which disseminates immediately to all interested parties (human or automated). y An event processing system has at least two components, (1) a sensor or source that senses events and emits event objects, and (2) a consumer or responder that receives and responds to event objects y Example: A mortgage company wants to make sure you have homeowner's insurance, so they could register for notification if your policy is canceled. They could also register for notification when a renewal is due and confirmation when the renewal is complete.

EDA Diagram

Event Processing Styles:

y Simple :When a notable event happens, initiates downstream action(s) y Stream : Both ordinary (orders, RFID transmissions) and notable events happen both are screened for notability and streamed to information subscribers y Complex: The cross event types ( notable or ordinary) may occur over a long period of time.
y EDA has four logical layers and they are : Event Generators, Event

Channel, Event Processing, Downstream Event driven Activity

y We will see Simple Example on Simple processing style of EDA

An online bookseller s inventory position optimization when a customer places an order online

What an event looks like in a Computer Language

Why EDA matters more now: Advantages

y On-line responses: Organizations can proactively inform people as soon as critical events occur. y Competitive pressure to deal with the increasing pace of business. y The inherent flexibility at each layer. what events are generated, how they are processed, and who receives them-is the real power of event. y Mix and Match: Services, Events and Business Processes . y Extremely loose coupled and well distributed y Easy implementation in languages for example in Swings in Java (ActionListener, ActionEvent)

EDA some Challenges

y High distribution, dynamic multi-path environment brings traceability

and management challenges. y Easily Create an Information Deluge . Both for People and Infrastructure y Lack of Interoperability Capacity y Marketplace Confusion: SOA, EDA, BPM

Conclusion
y A service-oriented architecture (SOA) can be combined with event

driven architecture technology to construct enterprise applications and systems in a way that allows more responsiveness and solves operational challenges y Zero-latency enterprise, the real-time enterprise, the event-driven enterprise and On Demand computing (IBM's term ) cannot be fully realized without event-driven design y Event-driven design will reduce the elapsed time of business processes and increase enterprise agility through the use of specific design practices and technologies. By Roy Schulte