java - Why do people use Messaging when you can use Files and a Batch tool? -

We have 2 memory java components (a data grid and a olap cube).

We currently use a batch processing tool to load the data grid, and when we want to update user data, we dynamically create batch jobs. What I am thinking, we should extend our batch tool so that it can take the responsibility to load the data in a rather cube. In the context of data transfer, the data grid should write a file, copy it to the server, which runs on the olap cube, and the olap cube should be read in this file.

The second option that we have when the data grid is loading or implements an update, it sends a message in the queue. The OLAP cube will then read this message, and will call a service on the data grid to drag data. I am firm against this option because this file is not based, which means that the support team will have trouble understanding it.

So the question is, why should we use to send messages?

Because if you write your own transaction files, you need to worry about it:

• Is the transaction for the file written
• Whether the file is transmitted properly, completely, or exactly exactly.
• Whether or not the file has been completely read, and if not, where do you keep reading

Simultaneously, on the reliability issue of all types related to the actual media