Popular and deep understanding of JMS (i.e. Java Message Service)

JMS is very early, online is more so, but most of the summary is not too comprehensive and not too specific, in the existing learning resources based on their own experience, now re-summed up:

JMS is all called the Java Message Service (the Java Messaging Services), which is one of the Java EE Technical Specifications (it belongs to the technical specification for message-oriented middleware (MOM) on the Java platform) for accessing the messaging system (or sending messages to the messaging system or receiving messages to the messaging system) , and finally realize the message interaction between different application systems. Hehe, when you read this, I'm afraid I'm going to whisper-what's the damn "messaging system"? We know that through the same JDBC interface can be implemented by different systems to access the same relational database, then through the JMS interface we can implement different systems to access the same "message system", the more straightforward "message system" is equivalent to the database mentioned above: A relational database is a software that runs on a computer or server (such as Oracle, MySQL, or SQL Server) The messaging system is also a software that runs on a computer or server (such as Apache ACTIVEMQ or IBM WebSphere MQ). The above sentence not only points out what is the "message system", but also explains what the role of JMS--JMS is similar to JDBC: JDBC provides a set of public interfaces for accessing a wide variety of relational databases, which are implemented specifically by companies that develop database software, Just use their jar package for development), and JMS provides a set of interfaces for accessing different messaging systems (these interfaces are specifically implemented by companies that develop message system software, just by using their jar packages for development).
Applications that use JMS are called JMS clients, and message systems that hold messages and deliver messages are called JMS PROVIDER,JMS applications by "multiple JMS clients" (JMS clients that send messages are called producers (producer) and JMS that receive messages The client is called the consumer (consumer), and the same JMS client can be either a producer or a consumer, and a business system consisting of a JMS Provider. JMS enables us to send messages from one application to another through the messaging service (that is, JMS Provider, sometimes referred to as a message broker or a messaging server).
The programming process for JMS is simple, and is summarized as: Application A (message producer) sends a message to a message server (for example: ActiveMQ) to a destination (Destination), The message server (for example: ActiveMQ) forwards the message to Application B (message consumer). Because application A and application B do not have direct code-related connection, both implementations understand the occasional. Such as:

Not finished ....

Popular and deep understanding of JMS (i.e. Java Message Service)