Orientated architecture Events

Orientated architecture events (of English Event Driven Structures, or EDA) is a form of architecture of mediation which is a model of applicative interaction implementing services (component software) answering external requests:

with a strong internal coherence (by the use of a XML, interchange format pivot generally), external
and couplings release (by the use of events)

In opposition to the Orientated architecture services (SOA) where a “supplier” renders a service at the request of a consumer; in architecture EDA, a “service” prevents by emission of an event which it carried out a given operation. It is to the Potential customers to treat this event.

With the SOA it is a very effective answer to the problems which meet the companies in terms of reutilisability, interworking and reduction of coupling between the various systems which implement their information systems.

Architectures EDA were popularized with the appearance of standards for the places on the market and the systems of auction.

They apply part of the principles of urbanization.

An orientated architecture events, rests mainly on a bus having functionalities of subscription and publication (publish and Subscribe).

Example

One can quote Sotheby' S, which set up an architecture of the type EDA for its management system of the biddings (inscription of the purchasers, management of the biddings with alarms,…) who deals with at the same time network Intranet and the requests of his Web site and his telephone plate.

Concepts

The coupling between services is a coupling releases and the communications all are asynchronous.

The service can:

to be coded in any language,
to be carried out on any platform (material and software).

The service must:

to subscribe with the events which it wishes to treat
to treat the events to which it is subscribed without prejudging any order and emitting an event report of the action which he has just carried out
to provide the events that he is suceptible to emit of which the structures are publiése,
to be autonomous (to have all the necessary informations with his execution: no concept of state)
to respect a whole of contracts (operating rules).

The directory of services

The directory of services reference the whole of the services and their events (and the associated contracts) available within IF, it takes an active part thus in the implementation of a dynamic cartography of IF.

The bus Publish & Subscribe

In an architecture EDA, the bus has a role of mediator (middleware) between the originating department of the event and the potential consumers, it thus makes it possible to carry out the loose coupling. The bus can also provide a range of services:

on the basis of patterns EIP (Enterprise Pattern Integration), to provide functionalities of Split, combines, etc making it possible to combine the call on several services,
of the functionalities of versioning of service,
of the functionalities of supervision and control (with SLA) of the services.

The event

A event can be defined like " a significant change of état". For example, when a customer buys a painting, the table passes from the state " with vendre" with the state " vendu" and the system of invoicing will start the emission on reception of this event of the invoice, the same state will be treated by the service commission to calculate the honaraires of the auctioneer.

This model of architecture is very flexible and with a coupling very releases. The consumers of an event must subscribe (subscribe) with an intermediary of management of event (the bus) and the producer of the event must publish it near this manager (the bus). When the manager of évènemet receives an event of a producer, it diffuses it (forward) with the consumers concerned. If the consumer is injoingnable, the manager can preserve the message and issue it later. This means of transmissioon of events rests on a bus of message " blind and forward" .

To conceive an information system resting on an orientated architecture events makes it possible its applications to be built of more reactive, more flexible mamière and more flexible device.

Architecture EDA supplements the Orientated architecture services (SOA) because the services can be activated by triggers which are the events.

Structure of an event

An event includes/understands 2 parts, a heading (vent header) and the message (vent body). The heading includes/understands information like its name, its type, and a time-stamping (timestamp of the event). The message is the part which describes the cause of the event (table X was sold for a price Y with purchaser Z).

See too

Vent-driven programming
Orientated architecture Services
Complex Vent Processing

Articles

Article giving the differences between EDA and SOA: How EDA important extends SOA and why it is by Jack van Hoof.

References

Random links: