This chapter shows you how to design message-driven beans with the Java Message Service (JMS). In enterprise systems, message-driven beans communicate with other objects asynchronously (no waiting). Designs with message beans are scalable because message beans are stateless. The container uses instance pooling to handle a large number of messages concurrently.
Here are the key points from this chapter.
In a synchronous architecture, clients are tightly coupled with each other. A client's thread blocks until a method completes. Adding or removing clients is difficult.
In an asynchronous architecture, clients are loosely coupled and communicate through a centralized server. Method calls return without blocking. Adding or removing ...