Paradigms of communication

From GreenVulcano Wiki
Revision as of 00:30, 11 February 2012 by Anonymous (talk) (Asynchronous-Synchronous)
Jump to: navigation, search

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-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

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:

  1. GreenVulcano® ESB, using a plugin, invokes the server and waits for the response into a queue jms, bmq, etc.
    plugin->server->jms
  2. GreenVulcano® ESB enqueues into a jms queue shared with server and waits for the response into another jms queue.
    jms->server->jms

Asynchronous-Synchronous

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:

  1. 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.
    Adapter->plugin->server->plugin
  2. 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.
    Adapter->plugin->server->jms
  3. 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.
    jms->plugin->server->jms

Asynchronous-Asynchronous