3. What integration paradigms does ESA support?
a) Service-orientated architecture (SOA)
b) Message-driven architecture
c) Event-driven architecture
d) Model-driven architecture
In order to support a comprehensive SOA (request/response, publish and subscribe, events, etc.) an ESA supports service-oriented, message-driven as well as event-driven architecture. In a service-orientated architecture, applications communicate through reusable services that have clear, well-defined interfaces. Service-orientated communication makes use of the underlying event and messaging communication models.
In a message-driven architecture, applications send messages via an ESA/ESB? to receiving applications. In an event-driven architecture applications create and consume messages independently of one another. In the context of SOA model-driven architecture (MDA) provides a mechanism to "manage technology". Model-driven architecture allows you to implement and manage the "meta-bus" (an ESB). MDA covers a number of specifications that have been standardised by the Object Management Group (OMG). Model-driven development allows you to stay technology independent while still being able to generate highly targeted code. SAP's WebDynpro paradigm and Visual Composer are both big supporters of model-driven development.
This was first published in September 2005