Difference between revisions of "Paradigms of communication"
(→Synchronous-Asynchronous) |
(→Synchronous-Asynchronous) |
||
| Line 37: | Line 37: | ||
The decoupling of communication can happen in two ways: | The decoupling of communication can happen in two ways: | ||
| − | # {{GVESB}}, using a [[Plugins|plugin]], invokes the | + | # {{GVESB}}, using a [[Plugins|plugin]], invokes the server and waits for the response into a queue jms, bmq, etc. [[File:ParadigmSA1.jpg|none|thumb|plugin->server->jms]] |
| − | # {{GVESB}} enqueues into a jms queue shared with server and | + | # {{GVESB}} enqueues into a jms queue shared with server and waits for the response into another jms queue.[[File:ParadigmSA2.jpg|none|thumb|jms->server->jms]] |
===Asynchronous-Synchronous=== | ===Asynchronous-Synchronous=== | ||
Revision as of 17:42, 10 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 | 1 | Synchronous |
