Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

Event-driven architecture is a software architecture and model that is used for application design. With the deployment of an event-driven system; the capturing, communicating, processing, and persistence of events form the core components of the solution. The characteristics of this model will differ from a traditional request-driven model.

The main benefit of an event-driven architecture is it enables applications to trap events as they occur and process complex multi-step decisions in real-time mode. This method will maximize application responsiveness and enable businesses to ensure improved customer experience and optimized network utilization converting event interactions into stronger profits.

Some customers use the event-driven architecture for their internal systems if their solution is complex. This is the reason why this knowledge can be beneficial.

This is the reason why via standard Camel component can be created connection with different JMS systems as are:

  • Apache ActiveMQ

  • Apache Kafka

  • IBM WebSphere

  • No labels