Architecture - Event Driven

Architecture consists of specifications for software, hardware and networks for a particular business solution. Architectural artifacts present the structural components of a solution for an significant business challenge. Scope, requirements and use case provide essential inputs to develop meaningful document artifacts for a successful solution.

Presently event-driven-architecture (EDA) has emerged as a predominant influence on architectural designs. Traditionally architecture is divided into components based on functional entities for a business solution such as customer-relationship-management, investor services, financial, supply chain management, marketing, project management, governance, retention, procurement and quality assurance. The EDA approach identifies business components by types of transactions or events--services. Conveniently event analysis maintains the same grouping of business services components however the purpose of each service is focused on a result oriented workflow of events. At the base of EDA is the service-oriented-architecture (SOA) which facilitates business transactional events with service endpoints, channels, and protocols.

Event driven architecture emphasizes the importance of network message policies along with SOA implementations of endpoint, channel and protocol specifications. Enterprise-service-bus (ESB) technology is an crucial implementation to orchestrate policy workflows within and between each business service.