Event-Driven Architecture ( Considerações (3.2 Rating: High (Ease of…
2.2 Event Channel
2.3 Event Processor
no central event mediator
the message flow is distributed across the event processor components
This topology is useful when you have a relatively simple event processing flow and you do not want(or need) central event or orchestration
1.2 Event Queue
1.3 Event Mediator
1.4 Event Chanel
1.5 Event Processor
contain the application business
logic necessary to process the processing event.
boxes with similar functions
Event channels are used by the event mediator to asynchronously pass specific processing events related to each step in the initial event to the processors.
the steps contained within the initial event.
through open source integration hubs such as Spring Integra‐
tion, Apache Camel, or Mule ESB.
can be a message queue
a web service endpoint
sent by the user
architecture pattern is a relatively complex pattern
to implement, primarily due to its asynchronous distributed nature.
3.1 Raiting: Low
While individual unit testing is not overly difficult, itdoes require some sort of specialized testing client or testing tool to generate events
3.2 Rating: High
Ease of deployment
Overall this pattern is relatively easy to deploy due to
the decoupled nature of the event-processor components.
Overall agility is the ability to respond quickly to a
constantly changing environment.
while it is certainly possible to implement an event-driven architecture that does not perform well due to all the messaging infrastructure
Scalability is naturally achieved in this pattern through
highly independent and decoupled event processors.