Project

General

Profile

Feature #4285

extend cross-session pub/sub to allow subscriptions/notifications between multiple FWD servers

Added by Greg Shah over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD

History

#1 Updated by Greg Shah over 1 year ago

Today, the cross-session pub/sub only works within a single FWD server. It does not matter if there are multiple applications running within the server, but if the applications (or instances of the same application) are in separate FWD servers then the facility cannot be used.

This task is meant to explore (and possibly implement) the idea of cross-server pub/sub. To implement it:

  • remote subscriptions must be made and managed
  • remote notifications must be made when needed
  • a security plugin will be needed
  • we don't need routing unless we enable multi-node hops

#2 Updated by Igor Skornyakov over 1 year ago

In my practice, this kind of cross-server communication was typically implemented on the top of JMS (with a standalone MQ server or an embedded one). For example, the open-source Apache ActiveMQ (https://activemq.apache.org/) provides out-of-the-box solutions for many problems regarding scalability and reliability which may arise in this kind of communication.

#3 Updated by Greg Shah over 1 year ago

We should definitely consider this idea. The internal communication protocol is message based and we have both queueing and routing built in. The ApacheMQ will have scalability facilities that we don't have.

Another idea is to expose the internal messaging protocol of FWD by implementing the JMS interface. The advantage of this would be a simpler implementation rather than layering a separate MQ solution into FWD (with extra ports, separate FWD security setup, more firewall rules....).

Anyway, it is worth considering.

Also available in: Atom PDF