The ‘Event-Driven Business Architecture’ is the idea of a software architecture that centers business applications on events and processes. In the following, I will explain its core concepts and describe how building business applications around events can enhance architectural flexibility.
What is an Event?
When we talk about ‘Event-Driven Business Architecture’, one of the first questions that naturally arises is: What exactly is an event? Let’s examine the characteristics of an event in detail.
First of all, an event is something that happens, either unexpectedly or as a planned occurrence. Events are omnipresent in our business world – from a new customer request to the sending of an invoice or the receipt of a payment. When these events occur regularly and follow a defined sequence, we speak of a process. For example, the three events mentioned could be part of an order process.
From a technical perspective, an event has several properties that describe its nature. The most fundamental property is the timestamp indicating when the event occurred. Another crucial property is the actor who initiated the event – this could be a customer submitting a new request, an employee creating an invoice, or a technical system such as a transport system’s control unit sending tracking information. And last but not least, we have the kind of the event which describes the business context it occurred in. This typically relates to what we call a ‘business process’ and defines the formal framework the event is bound to.
Continue reading “Event-Driven Business Architecture (EVENT34)”
