3 Star 31 Fork 35

huan1993 / 消息队列的简单使用

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
Apache-2.0

rabbitmq

项目介绍

对消息队列RabbitMQ简单的使用,以及编写一些示例。

代码结构

rabbitmq
│ |- 父项目
├─rabbitmq-helloword
│ |- rabbitmq的入门示例,一个简单的生产者和消费者示例  
│    1、消费端消息的限流,(basicQos,必须要手动签收)   
├─rabbitmq-advance
│ |- rabbitmq的高级示例
├──────── returnlistener(处理未被正确路由的消息 http://huan1993.iteye.com/blog/2429061)
│               1、mandatory:参数的使用  
│               2、用于获取到没有路由到消息队列中的消息。
│               3、如果没有触发ReturnListener的注意事项(RabbitMQ配置的内存和磁盘限制) http://www.rabbitmq.com/alarms.html
│──────── alternateexchange(处理未被正确路由的消息 http://huan1993.iteye.com/blog/2429061)
│               1、当消息从生产者交换器出发,没有合适的routingKey,那么会交给这个交换器的 备份交换器(alternate-exchange)   
│──────── defaultexchange(默认交换器)
│               1、默认的交换器是 "" ,并且是直连的交换器
│               2、新建的队列默认会自动绑定到默认的交换器上,且routingKey是队列的名称
│──────── topic(topic交换器-发布订阅)
│               1、# 匹配一个或多个
│               2、* 匹配一个  
│               3、eg:
│                     bindingKey : 
│                         goods.*      
│                         goods.#                
│                     routingKey:
│                         goods.apple           ==> 可以被上方2个都匹配上
│                         goods.shopping.apple  ==> 只可以被 goods.# 匹配上           
│──────── produceconfirm(服务端消息确认 http://huan1993.iteye.com/blog/2432156)   
│           有时候我们消息生产者,需要知道消息是否到达了RabbitMQ服务器,那么就需要进行消息确认了
│           |- confirmlistener(confirm异步确认)   
│           |- tx(事务确认)  
│──────── dlx(死信队列和延时队列的使用 )
│           |- 死信队列 和 延时消息 整合成一个延时队列的使用例子 
├─rabbitmq-spring  
│ |- spring和rabbitmq的整合示例(http://huan1993.iteye.com/blog/2432329)    
│       |- configuration rabbitmq和spring整合的配置    
│       |- test 各种测试  
│           |- DynamicSimpleMessageListenerContainerTest  
│                   |- 测试动态的添加对队列的监听和移除对队列的监听  
│                   |- 还可以动态修改其它的属性  
│           |- RabbitAdminService  
│                   |- rabbitAdmin 的简单使用,比如创建队列删除队列等等  
│           |- RabbitTemplateTest  
│                   |- 使用rabbitTemplate发送消息等  
├─rabbitmq-springboot  
│ |- springboot整合rabbitmq(http://huan1993.iteye.com/blog/2432697)  
│       |- @RabbitListener 标注的方法中的bindings会自动进行创建队列、转换器和绑定等    
│           |- 标注在类上: 为当前类中所有存在@RabbitHandler标注的方法服务  
│           |- 标注在方法上:为每个方法创建一个监听容器      
│       |- @RabbitHandler 标注的方法会使用用于处理接收到的消息  
│       |- 如果是接收javabean,注意事项如下:  
│           > 1、方式一:发送方和接收方的发送的实体类必须实现序列化接口,并且包名需要相同  
│           > 2、方式二:使用 @Payload 注解  
│           > 3、方式三:使用自定义 MessageConverter可能需要重写里面的方法  
│           > 4、上面的方式组合使用      
├─rabbitmq-springboot-advanced  
│ |- springboot整合rabbitmq(http://huan1993.iteye.com/blog/2432697)  
│       |- 使用@Bean方式自动实现队列、交换器、绑定的创建    
│       |- 使用@RabbitListener实现队列消息的监听   
│       |- 实现生产者消息确认
│           |- spring.rabbitmq.template.mandatory = true 设置成true  
│           |- spring.rabbitmq.publisher-confirms = true 设置成true      
│       |- 实现死信交换器(过期的消息、basic.nack或basic.reject且requeue参数为false或队列满的消息将进入此交换器)        
│           |- 申明队列的时候设置 x-dead-letter-exchange 参数  
│       |- 实现备份交换器(alternate-exchange),未被正确路由的消息将会经过此交换器    
│           |- 申明交换器的时候设置 alternate-exchange 参数  
│─使用docker搭建rabbitmq集群(https://blog.csdn.net/fu_huo_1993/article/details/102986327)  
│─RabbitMQ顺序消息消费,一个队列只有一个消费者  
├─rabbitmq-springboot-multi (https://blog.csdn.net/fu_huo_1993/article/details/107846901)  
│ |- springboot整合多个rabbitmq  
│       |- 配置多个RabbitMQ      
│       |- 往Spring容器中动态加入Bean    
│       |- 如果配置是从数据库中加载的,或则是通过CommandLineRunner来实现的,在需要调用SimpleMessageListenerContainer#start 方法

kafka  
├─基本文章 
│   |- 1、kafka集群的搭建(https://blog.csdn.net/fu_huo_1993/article/details/111089375)
│   |- 2、kafka-eagle监控界面搭建(https://blog.csdn.net/fu_huo_1993/article/details/111982652)
│   |- 3、kafka的基本概念(https://blog.csdn.net/fu_huo_1993/article/details/112111299)  
├─kafka-api(https://blog.csdn.net/fu_huo_1993/article/details/112398024) 
│   |- 生产者
│       |- KafkaProducer线程安全的,可以在多线程中使用。
│       |- 消息发送的key和value的序列化
│       |- 自定义分区的使用
│       |- 自定义拦截器的使用
│       |- 消息发送完成后的回调使用
│   |- 消费者
│       |- 消息接收的key和value的序列化
│       |- 指定消费者组
│       |- 自动提交 offset (生产环境可以使用手动提交offset)
│       |- 重置消费者的偏移量,此配置生效的条件
│       |- 自定义消息消费拦截器
│       |- 每次从服务器获取多少数据
├─kafka-springboot(https://blog.csdn.net/fu_huo_1993/article/details/113482869) 
│       |- springboot 和 kafka 整合的一个小例子
│       |- 消费者消息的手动ack

微信公众号

更多内容请关注微信公众号

更多内容请关注微信公众号

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: You must give any other recipients of the Work or Derivative Works a copy of this License; and You must cause any modified files to carry prominent notices stating that You changed the files; and You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "{}" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2018 huan1993 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

简介

各种主流的消息队列的使用案例。 展开 收起
Java
Apache-2.0
取消

发行版

暂无发行版

贡献者

全部

近期动态

加载更多
不能加载更多了
Java
1
https://gitee.com/huan1993/rabbitmq.git
git@gitee.com:huan1993/rabbitmq.git
huan1993
rabbitmq
消息队列的简单使用
master

搜索帮助