Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Event-driven architecture

An overview
by

Markus Gallagher

on 4 December 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Event-driven architecture

event driven architecture
call stack --> synchronized execution
assumptions:
one things happens at a time
we know what should happen in what order
we know who can provide a needed function
execution happens in a single virtual machine
single memory space / single development team
command-and-control (traditional)
the real world is event-driven
reactive behavior vs. planning in advance
fire and forget messaging
interconnection of components and systems
giving up control...
subscribe and react
components assembled at run-time
broadcast communication
timeliness
asynchronous
fine grained events
complex event processing
event ontology
classification hierarchy
categories
characteristics of eda
a significant change in state
initiated outside of scope (publisher)
handled inside of scope (handler)
past tense (OrderPlaced, PaymentReceived, ...)
uniquely identifiable
time relevant, not time sensitive
events
elegance
loose coupling (space, time, synchronization)
distributed
more responsive
better for asynchronous env
[testa|scala|extensi|flexi]bility
advantages
maintance overhead
less build-time validation
debugging difficult (sender/listener problem)
undesirable compositions / uncertainty
visualizing system state is difficult
disadvantages
obeys
Open Closed Principle
Single Responsibility
complements soa (more loosely coupled)
eda...
configuration / management
visualization tools for system state
instant replay
tips
event life-cycle
event generator
event channel
event processing
downstream activity
event processing styles
simple
stream
complex (cep)
event types
business
lifecycle
management
event structure
header
body
web
http://www.eaipatterns.com/docs/EDA.pdf
http://en.wikipedia.org/wiki/Event-driven_architecture
http://www.omg.org/soa/Uploaded%20Docs/EDA/bda2-2-06cc.pdf
http://cs09501.blogspot.ch/2012/09/architectural-styles-event-driven.html

books
enterprise integration patterns (hohpe, woolf)
patterns of enterprise application architecture (fowler)
soa patterns (arnon rotem-galz-oz, eric bruno, udi dahan)
References
stack
soa
eda
developer
developer
developer
coffee machine
coffee machine
coffee machine
FillCup
WakeUpService
FellAsleep
query and command
event driven
source: programming without a call stack - event-driven architecture, gregor hohpe, 2006
source: http://cs09501.blogspot.ch/2012/09/architectural-styles-event-driven.html
http://ptrthomas.wordpress.com/2006/06/06/java-call-stack-from-http-upto-jdbc-as-a-picture/
shameless plug...
markus.gallagher@edorex.ch
http://www.edorex.ch/eda
architect's dream
developer's nightmare
Full transcript