Routing

  • In the previous tutorial we built a simple logging system. We were able to broadcast log messages to many receivers.
  • In this tutorial we're going to add a feature to it ,we're going to make it possible to subscribe only to a subset of the messages.For example,we'll be able to direct only critical error messages to the log file,while still being able to print all of the log messages on the console.

Bindings

  • In previous examples we were already creating bindings. You may recall code like:
  •   channel.queueBind(queueName,EXCHANGE_NAME,"");
  • A binding is a relationship between exchange and queue.This can ba simply read as: the queue is interested in messages from this exchange.
  • Bindings can take an extra routingKey parameter.To avoid the confusion with a basic_publish parameter we're going to call it a binding key.This is how we could create a binding with a key:
  •   channel.queueBind(queueName,EXCHANGE_NAME,"black");
  • The meaning of a binding key depends on the exchange type.The fanout exchanges,which we used previously,simply ignored its value.

Direct exchange

  • Our logging system form the previous tutorial broadcast all messages to all consumers.We want to extend that to allow filtering messages based on their severity.For example we may want a programs which write logs messages to the disk to only receive critical errors,and not waste disk space on warning or info log messages.

  • We were using a fanout exchange ,which doesn't give us much flexibility - it's only capable of mindless broadcasting.

  • We will use a direct exchage instead.The routing algorithm behind a direct exchange is simple - a message goes to the queues whose binding key exactly matches the routing key of the message.

  • To illustrate that,consider the following setup:

  • In this setup, we can see the direct exchange x with two queues bound to it.The first queue is bound with binding key orange, and the second has two bindings, one with binding key black and the other one with green.

  • In such a setup a message published to the exchange with a routing key orange will be routed to queue Q1.Messages with a routing key of black or green will go to Q2.All other messages will be discarded.

Multiple bindings

  • It is perfectly legal to bind multiple queues with the same binding key.In our example we could add a binding between X and Q1 with binding key black.In that case,the direct exchange will behave like fanout and will broadcast the message to all the matching queues.A message with routing key black will be delivered to both Q1 and Q2.

Emitting logs

  • We'll use this model for our logging system. Instead of fanout we'll send messages to a direct exchange.We will supply the log severity as a routing key.That way the receiving program will be able to select the severity it wants to receive. Let's focus on emitting logs first.
  • As always, we need to create an exchange first:
  •   channel.exchangeDeclare(EXCHANGE_NAME, "direct");
  • And we're ready to send a message:
    channel.basicPublish(EXCHANGE_NAME, severity, null, message.getBytes())
  • To simplify things we will assume that 'severity' can be one of 'info', 'warning', 'error'.

Subscribing

  • Receiving messages will work just like in the previous tutorial, with one exception - we're going to create a new binding for each severity we're interested in.
  •   String queueName = channel.queueDeclare().getQueue();
    
      for(String severity : argv){
    channel.queueBind(queueName, EXCHANGE_NAME, severity);
    }

Code

  •   public class EmitLogDirect {
    private static Log log = LogFactory.getLog(EmitLogDirect.class);
    private static final String EXCHANGE_NAME="direct_logs";
    public static void main(String[] argv)
    {
    ConnectionFactory connFactory = new ConnectionFactory();
    connFactory.setHost("localhost");
    Connection conn=null;
    Channel channel=null;
    try {
    conn=connFactory.newConnection();
    channel=conn.createChannel();
    channel.exchangeDeclare(EXCHANGE_NAME, BuiltinExchangeType.DIRECT);
    String[] severity={"info","warning","error"};
    String message="hello,world";
    for(String s:severity)
    {
    channel.basicPublish(EXCHANGE_NAME,s,null,message.getBytes());
    System.out.println("sent:"+s+" "+message);
    } } catch (IOException e) {
    log.error(e);
    } catch (TimeoutException e) {
    log.error(e);
    } finally {
    if (channel!=null)
    {
    try {
    channel.close();
    } catch (IOException e) {
    log.error(e);
    } catch (TimeoutException e) {
    log.error(e);
    }
    }
    if (conn!=null)
    {
    try {
    conn.close();
    } catch (IOException e) {
    log.error(e);
    }
    }
    }
    }
    }
    public class ReceiveLogDirect {
    private static Log log= LogFactory.getLog(ReceiveLogDirect.class);
    private static final String EXCHANGE_NAME="direct_logs";
    public static void main(String[] argv)
    {
    ConnectionFactory connFactory = new ConnectionFactory();
    connFactory.setHost("localhost");
    /*Connection conn=null;
    Channel channel=null;*/
    try {
    final Connection conn=connFactory.newConnection();
    final Channel channel=conn.createChannel();
    channel.exchangeDeclare(EXCHANGE_NAME, BuiltinExchangeType.DIRECT);
    String queueName=channel.queueDeclare().getQueue(); String[] severity={"info","warning","error"};
    for (String s:severity)
    {
    channel.queueBind(queueName,EXCHANGE_NAME,s);
    }
    Consumer consumer=new DefaultConsumer(channel){
    @Override
    public void handleDelivery(String consumerTag, Envelope envelope, AMQP.BasicProperties properties, byte[] body) throws IOException {
    String message=new String(body,"UTF-8");
    System.out.println("receive:"+envelope.getRoutingKey()+" "+message);
    try {
    Thread.sleep(1000);
    } catch (InterruptedException e) {
    log.error(e);
    }finally {
    channel.basicAck(envelope.getDeliveryTag(),false);
    }
    }
    };
    channel.basicConsume(queueName,false,consumer);
    } catch (IOException e) {
    log.error(e);
    } catch (TimeoutException e) {
    log.error(e);
    } finally {
    }
    }
    }
  • Firstly,run ReceiveLogDirect.java 进行消息监听
  • Secondly,run EmitLogDirect.java 发送消息

Summary

  • 生产者将消息发送到路由器,然后消费者创建队列绑定到路由器(通过routing key),接着路由器将生产者发送的消息与消费者创建的队列进行匹配(使用binding key也就是routing key),将匹配的消息发送到队列由消费者读取。

6、Routing的更多相关文章

  1. ASP.NET MVC 入门3、Routing

    本系列文章基于Microsoft ASP.NET MVC Beta. 在一个route中,通过在大括号中放一个占位符来定义( { and } ).当解析URL的时候,符号"/"和& ...

  2. [转]ASP.NET MVC 入门3、Routing

    在一个route中,通过在大括号中放一个占位符来定义( { and } ).当解析URL的时候,符号"/"和"."被作为一个定义符来解析,而定义符之间的值则匹配 ...

  3. ASP.Net MVC开发基础学习笔记:三、Razor视图引擎、控制器与路由机制学习

    一.天降神器“剃须刀” — Razor视图引擎 1.1 千呼万唤始出来的MVC3.0 在MVC3.0版本的时候,微软终于引入了第二种模板引擎:Razor.在这之前,我们一直在使用WebForm时代沿留 ...

  4. ASP.Net MVC开发基础学习笔记(3):Razor视图引擎、控制器与路由机制学习

    一.天降神器“剃须刀” — Razor视图引擎 1.1 千呼万唤始出来的MVC3.0 在MVC3.0版本的时候,微软终于引入了第二种模板引擎:Razor.在这之前,我们一直在使用WebForm时代沿留 ...

  5. 柯南君:看大数据时代下的IT架构(7)消息队列之RabbitMQ--案例(routing 起航)

    二.Routing(路由) (using the Java client) 在前面的学习中,构建了一个简单的日志记录系统,能够广播所有的日志给多个接收者,在该部分学习中,将添加一个新的特点,就是可以只 ...

  6. Spring Cloud Zuul网关 Filter、熔断、重试、高可用的使用方式。

    时间过的很快,写springcloud(十):服务网关zuul初级篇还在半年前,现在已经是2018年了,我们继续探讨Zuul更高级的使用方式. 上篇文章主要介绍了Zuul网关使用模式,以及自动转发机制 ...

  7. Angular基础(七) HTTP & Routing

    ​ 一.HTTP a)Angular提供了自己的HTTP库来调用外部API,为了能够在等待API响应的过程中继续与界面交互,采用异步HTTP请求的方式. b)Get请求,首先导入Http, Respo ...

  8. 4.1 Routing -- Introduction

    一.Routing 1. 当用户与应用程序交互时,它会经过很多状态.Ember.js为你提供了有用的工具去管理它的状态和扩展你的app. 2. 要理解为什么这是重要的,假设我们正在编写一个Web应用程 ...

  9. RabbitMQ---3、c#实现

    1.EasyNetQ组件的使用 EasyNetQ组件的使用方式比较简单,跟很多组件都类似,例如:建立连接,进行操作做等等,对于EasyNetQ组件也是如此.(mq的升级,用于简化rabbitmq应用代 ...

随机推荐

  1. 修改postgresql 密码

    sudo -u postgres psql -c "alter user postgres password '123456';"

  2. 8.gitlab 邮件设置

    这个我没做实验.  视屏里面说的 126的 邮箱限制少点. 建议用126的 邮箱. 参考视屏  jenkins+gitlab+插件\1\7(07-gitlab备份恢复)   最后的一点部分. 需要在配 ...

  3. Ubuntu环境下打开Firefox报错: Firefox is already running, but is not responding.

    在ubuntu下启动firefox可能会报错 Firefox is already running, but is not responding. To open a new window, you ...

  4. 【转】基于Bootstrap的超酷jQuery开关按钮插件

    基于Bootstrap的超酷jQuery开关按钮插件

  5. luoguP5227 [AHOI2013]连通图

    题意 虽然没用线段树,但是仍然是线段树分治的思想. 考虑分治询问序列,假设当前在\([l,r]\),我们将\([1,l-1]\)和\([r+1,Q]\)的与\([l,r]\)内不重复的边都连上了. 先 ...

  6. VMWare虚拟机提示:另一个程序已锁定文件的一部分,打不开磁盘...模块"Disk"启动失败的解决办法

    重启了电脑之后,打开VMware就发现出现了“锁定文件失败,打不开磁盘......模块"Disk"启动失败.”这些文字 为什么会出现这种问题: 这是因为虚拟机在运行的时候,会锁定文 ...

  7. [mybatis] sql语句无错误,但是执行多条sql语句时,抛出java.sql.SQLSyntaxErrorException

    错误内容 org.springframework.jdbc.BadSqlGrammarException: ### Error updating database. Cause: java.sql.S ...

  8. vue_03day

    目录 作业: vue组件操作页面渲染: 组件渲染: 作业: vue组件操作页面渲染: 1.有以下广告数据(实际数据命名可以略做调整) ad_data = { tv: [ {img: 'img/tv/0 ...

  9. ES6-Symbol.iterator 迭代器

    一个数据结构只要部署了Symbol.iterator属性就能使用 for...of遍历 与 ...运算符 操作 Object身上没有Symbol.iterator,当直接使用时会报错 let obj ...

  10. ZooKeeper 入门看这篇就够了

    什么是 ZooKeeper? ZooKeeper 是一个分布式的,开放源码的分布式应用程序协同服务.ZooKeeper 的设计目标是将那些复杂且容易出错的分布式一致性服务封装起来,构成一个高效可靠的原 ...