Note that there are some explanatory texts on larger screens.

plurals
  1. POIs JMS the answer to the need for a persistent blocking queue?
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COJust be aware of the implementation of JMS that you are using and how the infrastructure is set up. Some implementations of JMS allow for multiple threads to read and process messages concurrently. This preservers FIFO from the standpoint of getting picked up by the queue, but does not necessarily preserve FIFO from the standpoint of when messages are processed. Again, check to see your implementation. If you are running JMS that supports concurrent reads, then just make sure it is tuned to disallow them. Or if you don't care, then you can ignore what I just said. :)
      singulars
    2. COThanks. It's OK if some of the data is slightly unordered as it can be sorted on event data. My concern with JMS is the overhead of integrating another library. There are a lot of different JMS implementations around - is there one that's easier to implement than others and that can run in an embedded fashion?
      singulars
    3. COI'd look for a JMS implementation that supports only the need to access it via the JMS 1.1 and/or 1.2 spec. This way you can just programmatically read and write from the queues using just the API. Only reason I mentioned implementation is that sometimes you have to configure certain things with the vendor implementation to turn on/off concurrency etc. In my case, we stick to IBM products, cause my company loves Big Blue. But you could probably get away with any implementation. In our case, I still tell our developers to stick to just the API and do nothing implementation specific.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload