Simulation JMS

[AvocadoMoon]

Problem

Background:
Current method for updating Java clients with information is to use JMS as the communication protocol handler, ActiveMQ as a Queue of messages, and MongoDB as a place to store the larger messages.

What Is Wrong With This System:
The problem with this entire system is not it's architecture, but instead the message type used by JMS. It uses java object serialization which makes the communication protocol brittle, being directly coupled to Java objects and their Java version.

Solution

Change the message type used by JMS to text (JSON or XML), which will require changes in ActiveMQ and MongoDB as well, but will make the communication significantly more flexible and potential to be used in other programming languages.

• Round trip test, ensuring that API clients can initialize the state machine, it continues internally with the simulation process giving update messages, and if requested by the client, to stop the entire simulation process.