Différences

Ci-dessous, les différences entre deux révisions de la page.

--- cours:ws-rest_and_ws-soap:eventing_lab2 [2018/04/05 06:35] – [LAB 2 : Web Service Eventing and Velib Project] tigli
+++ cours:ws-rest_and_ws-soap:eventing_lab2 [2018/04/05 06:41] (Version actuelle) – [LAB 2 : Web Service Eventing and Velib Project] tigli
@@ Ligne 3: / Ligne 3: @@
 |||
-// to combine Combining Service-Oriented Architecture and Event-Driven Architecture using an Enterprise Service Bus
+// to combine Service-Oriented Architecture and Event-Driven Architecture ...//
-The purpose of this add is to add an event driven
+The purpose of this lab is to superpose an event driven architecture to our past service oriented approach.
-As an extension of the "Velib" project, here we are going to add some event based clients of your Proxy Web Service. A Client may be then a subscriber to a specific city/station and receive the last number of avialable velib in this station. This information must be of course recent and no older than a given périod **T**
+As an extension of the "Velib" project, here we add some event based clients of your Proxy Web Service. A Client may be then a subscriber to a specific city/station and receive the last number of available velib in this station. This information must be of course recent and no older than a given period **T** specific to each client.
 === Interesting Reference to read about SOA / EDA hybrid architectures : Entreprise Service Bus ===
 ||
-[[https://www.ibm.com/developerworks/library/ws-soa-eda-esb/|Combining Service-Oriented Architecture and Event-Driven Architecture using an Enterprise Service Bus,Jean-Louis Maréchaux, IBM Developer Works, March 28 2006=]]
+[[https://www.ibm.com/developerworks/library/ws-soa-eda-esb/|Combining Service-Oriented Architecture and Event-Driven Architecture using an Enterprise Service Bus,Jean-Louis Maréchaux, IBM Developer Works, March 28 2006]]
 The Enterprise Service Bus is an architectural pattern that facilitates and simplifies business integration through transport, event and mediation services. It connects and mediates all communications and interactions between heterogeneous nodes, both in a ** Service-Oriented Architecture (synchronous one-to-one approach)** and an **Event-Driven Architecture (asynchronous many-to-many approach)**.