zoukankan      html  css  js  c++  java
  • Message Queue vs. Web Services?

     From stackoverflow.com 


    When you use a web service you have a client and a server:

    1. If the server fails the client must take responsibility to handle the error.
    2. When the server is working again the client is responsible of resending it.
    3. If the server gives a response to the call and the client fails the operation is lost.
    4. You don't have contention, that is: if million of clients call a web service on one server in a second, most probably your server will go down.
    5. You can expect an immediate response from the server, but you can handle asynchronous calls too.

    When you use a message queue like RabbitMQ, Beanstalkd, ActiveMQ, IBM MQ Series, Tuxedo you expect different and more fault tolerant results:

    1. If the server fails, the queue persist the message (optionally, even if the machine shutdown).
    2. When the server is working again, it receives the pending message.
    3. If the server gives a response to the call and the client fails, if the client didn't acknowledge the response the message is persisted.
    4. You have contention, you can decide how many requests are handled by the server (call it worker instead).
    5. You don't expect an immediate synchronous response, but you can implement/simulate synchronous calls.

    Message Queues has a lot more features but this is some rule of thumb to decide if you want to handle error conditions yourself or leave them to the message queue.

  • 相关阅读:
    python_网络编程struct模块解决黏包问题
    python_网络编程socket(UDP)
    python_网络编程socket(TCP)
    python_面向对象
    python_生成器
    python_迭代器
    linux实操_shell自定义函数
    linux实操_shell系统函数
    linux实操_shell读取控制台输入
    scrapy-redis 0.6.8 配置信息
  • 原文地址:https://www.cnblogs.com/mysic/p/5472774.html
Copyright © 2011-2022 走看看