[Info-vax] Large mailboxes

[Jan-Erik Söderholm]

Den 2020-11-30 kl. 14:17, skrev Jean-François Piéronne:
> 
> Le 30/11/2020 à 10:35, Jan-Erik Söderholm a écrit :
>> Den 2020-11-30 kl. 07:37, skrev Jean-François Piéronne:
>>>
>>> Le 29/11/2020 à 20:18, Arne Vajhøj a écrit :
>>> [snip]
>>>
>>>> RabbitMQ is a fine traditional message queue (Kafka is not
>>>> a traditional message queue - it is often called a
>>>> message stream processing service).
>>>>
>>>> RabbitMQ is probably the most popular non-Java
>>>> open source message queue.
>>>>
>>>
>>> Correct, and is language agnostic. Kafka is Java oriented.
>>>
>>> JF
>>>
>>
>> Now, without reading through a lot of docs, can one get
>> a quick answer to an easy question? :-)
>>
>> Is the VMS port of RabbitMQ both server and client?
>> Or does the VMS port need an "external" RabbitMQ server?
>>
>> I mean, if I'd like to look at a solution with RabbitMQ
>> to raplace our current VMS/mailbox IPC setup, can that be
>> done locally within our VMS Alpha systems?
> 
> There is a old port of the server, but my best advice is to deploy the
> server part on Linux, this is what all sites I knew have done.
> The last I have installed used a cluster of 3 RabbitMQ nodes and 2
> ha-proxy front-end.
> 
> Client part, no problem, including on old VMS version.
> https://foss.vmsgenerations.org/openvms/libraries/rabbitmq-c
> https://foss.vmsgenerations.org/openvms/wasd/rmqplus
> Python module:
> https://foss.vmsgenerations.org/openvms/python/modules/pika
> 
> JFP
> 

OK.
I have no idea if RabbitMQ is used within my client environment.
They have IBM MQ/WebSphere as their main messaging tool.

To have something simple to replace/complement our MBX based
IPC right now, I'd not like to involve any Linux in the picture.
It has to be VMS only if it is going to be used for VMS only.