Presentation on theme: "Event Driven Architecture"— Presentation transcript:
1Event Driven Architecture When we have to use an Event Driven Architecture?Initially, Current Practices and Future
2What we will cover here What is the Event Driven Apps? When is the Event Driven Architecture was started?What is the Benefit?When we have to use?What is the Implementation in the real world?What is the trend?
3What is the Event Driven Apps? What is an Event?What is in an Event?What is the Reaction when an Event fires?
4Ask Wiki!An event is a notable thing that happens inside or outside your businessThe term event is often used interchangeably to refer to both the specification (definition) of the event, and each individual occurrence (instance) of the eventEach event occurrence has an event header and event body as the delivered information
5How’s an Event being consumed? It should be Published!And then Fired!And someone must Listen!And he /she will give some Reaction!Or, just ignore it!...
11The Problem on the Action Synchronous ActionAsynchronous Action
12When is the Event Driven Architecture was started? Four years from now, "mere mortals" will begin to adopt an event-driven architecture (EDA) for the sort of complex event processing that has been attempted only by software gurus building operating systems or systems management tools, and sophisticated developers at financial institutions. (Roy Schulte, an analyst at Stamford, Conn.-based Gartner )
13What is the Benefit? Scalable Reaction based Staged Staged + Reaction =
14When we have to use? Samples: Best used for Asynchronous Flows of Work and InformationWhen you need a Fast Responsive in front, but Asynchronous process in the backgroundFire and Forget handlingSamples:The Web Server
15What else? (Quiz) Use these following key words: ReplicationSchedulerReportingSynchronizationMessengerThen add with word “Engine“
16What is the Implementation in the real world? SOA based implementationMessaging based solutionAutomation solutionWorkflow solution