Browse Prior Art Database

A Pub/Sub based HTTP communication method in complex network environments

IP.com Disclosure Number: IPCOM000245434D
Publication Date: 2016-Mar-10
Document File: 4 page(s) / 98K

Publishing Venue

The IP.com Prior Art Database

Abstract

This disclosure proposes a Pub/Sub method to enable HTTP communication among various components in a complex network environment, without changing the original service provider and service consumer in the HTTP based RESTful communication model.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 4

A Pub

A Pub/

//Sub based HTTP communication method in complex network environments

Sub based HTTP communication method in complex network environments

In a complex distributed system that consists of internal and external networks, i.e., internet and intranet, it is very challenging to ensure communication among various components across different networks. Typically, components in distributed system communicate via REST calls. However, in the complex network environment, direct REST communication doesn't work sometimes, since the inbound connections are not allowed in particular situations without network tunnel.

The above figure is an example of the complex network environment, where Network A and Network B's sub network2 don't allow any inbound connections.

This disclosure proposes a Pub/Sub method to enable HTTP communication among various components in a complex network environment, without changing the original service provider and service consumer in the HTTP based RESTful communication model.

In this method, each existing HTTP request/response is wrapped in message stream, transmitted in the Pub/Sub message bus, and then is recovered for request/response consumer. This approach solves the communicate problems in specific network environment with limited efforts while still keeping the

1


Page 02 of 4

REST mode with sync HTTP calls.

Architecture

2


Page 03 of 4

Core components

HTTP transmission contains core components of this idea. By using it, clients can communicate with services using HTTP calls even in network environments where clients cannot fetch responses from services directly with HTTP calls.

Besides the message bus, there're two important components in the HTTP transmission component: Message routerand Message handler.

Workflow of the Message router:

Intercept HTTP requests from the client.

1.


2.

Transform the HTTP request to a Pub message, and transmit the message to the message bus. The Pub message contains the target service's endpoint,

the resource that is requested, and a UUID generated for this request. Subscribe the request's UUID by transmitting a Sub message to the message bus.


3.


4.

Listen to and get corresponding response from the message bus.


5.

Return the response to the client.

Workflow of the Message handler:

Subscribe the service endpoint by sending a Sub message to the message bus.

1.


2.

Listen to and get a request from the message bus.


3.

Interact with the service, and get the corresponding response from the service.


4.

Transmit a Pub message to the message bus. The Pub message contains request UUID and the corresponding response.

Advantages

Enable HTTP...