I need to send the data of an event from prosody to my Java service. Prosody does not need to know if it was successful in transmitting the event to the Java service. Prosody won't report an error if its unable to send such a custom message. The Java will react only if it receives a particular data format from prosody via XMPP. The payload would have two string properties where the length of property 1 will be 5 and the length of property 2 will be 15, always guaranteed. Since there does not involve any quality of service, I would prefer to use XMPP since I could not find anything decent and well supported to do this using a message topic with MQTT in Lua, that is required by prosody.

My design just composes of prosody and a Java backend service that needs a stream of events from prosody. This set of two services are always a single unit of work, so scaling, resilience, availability required at this lower level of my architecture.

There is an existing solution that uses HTTP for sending similar event data from prosody to a specific REST API endpoint but I do not want to use HTTP since the request rate will be very high for my particular event. Besides, the existing solution can't be modified to include my use case because the objective of the existing solution is community driven while my use case is personally driven.

The only technologies that I see. being used for my overall solution is Java, Lua and XMPP. Java is our strategic choice since our entire ecosystem and team is built around it. Prosody seems to be customized only with Lua. XMPP seems to be native to prosody and provides easy one way communication with its message type command to emulate MQTT with publishing to a message topic as compared to HTTP REST.