ActiveMQ in Action

- 书名:ActiveMQ in Action
- 作者: BruceSnyder DejanBosanac RobDavies
- 格式:PDF
- 时间:2024-06-29
- 评分:
- ISBN:9781933988948
HIGHLIGHT ActiveMQ in Action is an example-rich tutorial that shows Java developers how to implement distributed messaging using ActiveMQ, and how to integrate ActiveMQ with Java and non-Java technologies. DESCRIPTION Applications in enterprises need to communicate, most commonly done by messaging. Apache ActiveMQ is an open-source implementation of the Java Message Service (JMS), which provides messaging in Java applications. ActiveMQ in Action is a thorough, practical guide to implementing message-oriented systems using ActiveMQ and Java. Co-authored by one of the leading ActiveMQ developers, Bruce Snyder, the book starts with the anatomy of a core Java message, then moves quickly through fundamentals including data persistence, authentication and authorization. Later chapters cover advanced features such as configuration and performance tuning, illustrating each concept with a running real-world stock portfolio application. Readers will learn to integrate ActiveMQ with Apache Geronimo and JBoss, and tie into both Java and non-Java technologies including AJAX, .NET, C++, Ruby, and the Spring framework. KEY POINTS The first book to focus purely on ActiveMQ Strong early demand through the Manning Early Access Program Real-world examples and in-depth walkthroughs Concise, developer-centric, In Action style Focused on best practices gained through authors' deep ActiveMQ experience Demonstrates using Apache Camel to utilize enterprise integration patterns
- 上一篇: 中国历史政治地理十六讲
- 下一篇: 紫木槿
-
望月2017-11-12这本书用来了解Active MQ的用法很不错。提纲挈领。
-
vongosling2014-01-28就是和现行的 版本差距有些远了,不过有些设计思想还是普适的
-
huey2016-01-14看了其中几章,略实用,英语太差是硬伤。
-
stephansun2011-10-29Using the request/reply pattern, envision that there are thousands of requestsentering the broker every second from many clients, all distributed across many hosts.In a production system, more than just a single broker instance would be used for thepurposes of redundancy, failover, and load balancing. These brokers would also bedistributed across many hosts. The only way to handle this many requests would be touse many workers. Producers can always send messages much faster than a consumercan receive and process them, so lots of workers would be needed, all of them spreadout across many hosts as well. The advantage of using many workers is that each onecan go up and down at will, and the overall system itself isn’t affected. The producersand workers would continue to process messa...
-
stephansun2011-10-287.3 Implementing request/reply with JMSAs described in earlier chapters, messaging is all about the decoupling of senders fromreceivers. Messages are sent by one process to a broker, and messages are received froma broker by a different process in an asynchronous manner. One style of system architecturethat can be implemented using JMS is known as request/reply. From a high level,a request/reply scenario involves an application that sends a message (the request)and expects to receive a message in return (the reply). Traditionally, such a systemdesign was implemented using a client-server architecture, with the server and the clientcommunicating in a synchronous manner across a network transport (TCP, UDP,and so on). This style of architecture certainly has scalability limitations,...
-
stephansun2011-10-28Request/reply messaging in JMS applicationsAlthough the JMS spec doesn’t define request/reply messaging as a formal messagingdomain, it does provide some message headers and a couple of convenienceclasses for handling basic request/reply messaging. Request/reply messaging is anasynchronous back-and-forth conversational pattern utilizing either the PTP domain orthe pub/sub domain through a combination of the JMSReplyTo and JMSCorrelationIDmessage headers and temporary destinations. The JMSReplyTo specifies the destinationwhere a reply should be sent, and the JMSCorrelationID in the reply messagespecifies the JMSMessageID of the request message. These headers are used tolink the reply message(s) to the original request message. Temporary destinationsare those that are created only ...
-
英文原版
-
英文原版
-
英文原版
-
英文原版
-
英文原版
-
英文原版
-
英文原版
-
英文原版