Difference between revisions of "Paradigms of communication"
(→Asynchronous-Synchronous) |
|||
| Line 58: | Line 58: | ||
===Asynchronous-Asynchronous=== | ===Asynchronous-Asynchronous=== | ||
| + | |||
| + | [[File:ParadigmAA.jpg|thumb|Asynchronous-Asynchronous]]The Asynchronous-Synchronous paradigm takes place following the Client -> {{GVESB}} -> Server direction. | ||
| + | |||
| + | |||
| + | The following table shows its properties: | ||
| + | {|class="gvtable" | ||
| + | ! !! Client !! GVESB Workflow Number !! Server | ||
| + | |- | ||
| + | | Communication || Asynchronous || 4 || Asynchronous | ||
| + | |} | ||
| + | |||
| + | The decoupling of communication might happen in sixteen ways: | ||
| + | # The Client sends a Request to {{GVESB}} through an adapter, {{GVESB}} sends it to the Server. The server elaborates the request and, using an adapter, sends the response to the Client (SendReply).[[File:ParadigmAA1.jpg|none|thumb|Adapter->Plugin->server->Adapter->Plugin]] | ||
| + | # The Client sends a Request to {{GVESB}} through an adapter, {{GVESB}} enqueues into a Server JMS queue. The server elaborates the request and, using an adapter, sends the response to the Client (SendReply).[[File:ParadigmAA2.jpg|none|thumb|Adapter->JMS->server->Adapter->Plugin]] | ||
| + | # The Client sends a Request to {{GVESB}} through an adapter, {{GVESB}} enqueues into a Server JMS queue. The server elaborates the request and, using an adapter, sends the response to the Client who enqueue it in a Client JMS queue (SendReply).[[File:ParadigmAA3.jpg|none|thumb|Adapter->Plugin->server->Adapter->JMS]] | ||
| + | # The Client sends a Request to {{GVESB}} through an adapter, {{GVESB}} sends to the Server. The server elaborates the request and, using an adapter, sends the response to {{GVESB}} who enqueue it in a Client JMS queue (SendReply).[[File:ParadigmAA4.jpg|none|thumb|Adapter->Plugin->server->JMS->Plugin]] | ||
| + | # The Client sends a Request to {{GVESB}} through an adapter, {{GVESB}} sends to the Server. The server elaborates the request and enqueues it into a {{GVESB}} queue which, through a Forward, sends the response to a Client JMS queue.[[File:ParadigmAA5.jpg|none|thumb|Adapter->Plugin->server->JMS->JMS]] | ||
| + | # The Client sends a Request to {{GVESB}} through an adapter, {{GVESB}} enqueues into a Server JMS queue. The server elaborates the request and enqueues it into a {{GVESB}} queue which, through a Forward, sends the response to the Client.[[File:ParadigmAA6.jpg|none|thumb|Adapter->JMS->server->JMS->Plugin]] | ||
| + | # The Client sends a Request to {{GVESB}} through an adapter, {{GVESB}} enqueues into a Server JMS queue from which a Forward sends it to the Server. The server elaborates the request and enqueues it into a {{GVESB}} JMS queue which, through a Forward, sends the response to the Client.[[File:ParadigmAA7.jpg|none|thumb|JMS->Plugin->server->JMS->Plugin]] | ||
Revision as of 01:00, 11 February 2012
Contents
Description
Depending on the type of communication (Synchronous / Asynchronous), on the role played by GreenVulcano® ESB (active / passive) and on the response management, it is possible to have from a minimum of one to a maximum of four operations constituting a single interaction client - server.
GreenVulcano® ESB Configuration
GreenVulcano® ESB is configured for managing four paradigms of communication:
- Synchronous - Synchronous
- Synchronous - Asynchronous
- Asynchronous - Synchronous
- Asynchronous - Asynchronous
Synchronous-Synchronous
The Synchronous-Synchronous paradigm takes place following the Client -> GreenVulcano® ESB -> Server direction.
The following table shows its properties:
| Client | GVESB Workflow Number | Server | |
|---|---|---|---|
| Communication | Synchronous | 1 | Synchronous |
Synchronous-Asynchronous
The Synchronous-Asynchronous paradigm takes place following the Client -> GreenVulcano® ESB -> Server direction.
The following table shows its properties:
| Client | GVESB Workflow Number | Server | |
|---|---|---|---|
| Communication | Synchronous | 1 | Asynchronous |
The decoupling of communication can happen in two ways:
- GreenVulcano® ESB, using a plugin, invokes the server and waits for the response into a queue jms, bmq, etc.
- GreenVulcano® ESB enqueues into a jms queue shared with server and waits for the response into another jms queue.
Asynchronous-Synchronous
The Asynchronous-Synchronous paradigm takes place following the Client -> GreenVulcano® ESB -> Server direction.
The following table shows its properties:
| Client | GVESB Workflow Number | Server | |
|---|---|---|---|
| Communication | Asynchronous | 2/3 | Synchronous |
The decoupling of communication might happen in three ways:
- The Client makes a request to GreenVulcano® ESB using an Adapter. GreenVulcano® ESB elaborates the request, and after eventually communication with others systems, invokes a Service into the Client system to communicate the response.
- The Client makes a Request to GreenVulcano® ESB using an Adapter. GreenVulcano® ESB elaborates the request, and after eventually communication with others systems, enqueues the response in a queue shared with Client.
- The Client enqueue a message, GreenVulcano® ESB dequeue it, an after eventually communication with others systems, enqueues the response in a queue shared with Client.
Asynchronous-Asynchronous
The Asynchronous-Synchronous paradigm takes place following the Client -> GreenVulcano® ESB -> Server direction.
The following table shows its properties:
| Client | GVESB Workflow Number | Server | |
|---|---|---|---|
| Communication | Asynchronous | 4 | Asynchronous |
The decoupling of communication might happen in sixteen ways:
- The Client sends a Request to GreenVulcano® ESB through an adapter, GreenVulcano® ESB sends it to the Server. The server elaborates the request and, using an adapter, sends the response to the Client (SendReply).
- The Client sends a Request to GreenVulcano® ESB through an adapter, GreenVulcano® ESB enqueues into a Server JMS queue. The server elaborates the request and, using an adapter, sends the response to the Client (SendReply).
- The Client sends a Request to GreenVulcano® ESB through an adapter, GreenVulcano® ESB enqueues into a Server JMS queue. The server elaborates the request and, using an adapter, sends the response to the Client who enqueue it in a Client JMS queue (SendReply).
- The Client sends a Request to GreenVulcano® ESB through an adapter, GreenVulcano® ESB sends to the Server. The server elaborates the request and, using an adapter, sends the response to GreenVulcano® ESB who enqueue it in a Client JMS queue (SendReply).
- The Client sends a Request to GreenVulcano® ESB through an adapter, GreenVulcano® ESB sends to the Server. The server elaborates the request and enqueues it into a GreenVulcano® ESB queue which, through a Forward, sends the response to a Client JMS queue.
- The Client sends a Request to GreenVulcano® ESB through an adapter, GreenVulcano® ESB enqueues into a Server JMS queue. The server elaborates the request and enqueues it into a GreenVulcano® ESB queue which, through a Forward, sends the response to the Client.
- The Client sends a Request to GreenVulcano® ESB through an adapter, GreenVulcano® ESB enqueues into a Server JMS queue from which a Forward sends it to the Server. The server elaborates the request and enqueues it into a GreenVulcano® ESB JMS queue which, through a Forward, sends the response to the Client.
