Geek Answers Handbook

When is messaging (like JMS) used for multithreading?

I am working on a data processing application in which concurrency is achieved by putting several units of work in a message queue that several instances of a message-driven object (MDB) are listening on. Besides achieving concurrency in this way, we have no particular reason to use the messaging infrastructure and MDB.

This made me wonder why this could not be achieved using multiple threads.

So my question is, in what situations can asynchronous messaging (e.g. JMS) be used as an alternative to multithreading as a means of achieving concurrency? What are some of the advantages / disadvantages of using one approach over another.

+6
source share
6 answers

It cannot be used as an alternative to multithreading; it is a way to implement multithreading. There are three main types of solutions:

  • You are responsible for both ends of the line;
  • You are responsible for sending data; or
  • You are responsible for receiving the data.

- , - /, . , . .

beans , , .

+6

, : .

, JMS- , XA .

+5

EJB , EJB. JMS . Java-, (, , ), .

JMS , .

+4

, , .
, .
, , .

+3

, . .

, JMS . java.util.concurrent , jetlang, .

+1

, , . JMS, . , , . . . , JMS. JMS. JMS, . , , .

Simply put, JMS may be a better alternative to multithreading, depending on the application architecture.

+1
source

More articles:


All Articles