Message Broker System with Parallel Persistence
    1.
    发明申请
    Message Broker System with Parallel Persistence 审中-公开
    具有并行持久性的消息代理系统

    公开(公告)号:US20160156502A1

    公开(公告)日:2016-06-02

    申请号:US14954731

    申请日:2015-11-30

    申请人: Informatica LLC

    摘要: A message broker computer includes a master broker, a plurality of slave message brokers and event stores. A client system sends messages for processing to the master broker. The master broker generates a message event in response to receiving such a message, and distributes the message event in parallel to the slave brokers and the event stores. Each of the event stores store the message event in persistent storage, and notifies the master broker that the message event has been persisted. The master broker considers the message stabilized n a quorum of the event stores. As the master broker does not take action until a messaging event is stabilized, in the event of failover, a new master broker is able to re-construct a broker state of the old master with no loss of data.

    摘要翻译: 消息代理计算机包括主代理,多个从属消息代理和事件存储。 客户端系统向主代理发送要处理的消息。 主代理器响应于接收到这样的消息而生成消息事件,并且将消息事件与从属代理和事件存储并行地分发。 每个事件存储将消息事件存储在持久存储器中,并通知主代理消息事件已被持久化。 主经纪人认为信息稳定在事件商店的法定人数。 由于主代理在消息传递事件稳定之前不采取行动,因此在发生故障转移时,新的主代理能够重新构建旧主服务器的代理状态,而不会丢失数据。

    Message broker system with parallel persistence

    公开(公告)号:US10904155B2

    公开(公告)日:2021-01-26

    申请号:US14954731

    申请日:2015-11-30

    申请人: Informatica LLC

    摘要: A message broker computer includes a master broker, a plurality of slave message brokers and event stores. A client system sends messages for processing to the master broker. The master broker generates a message event in response to receiving such a message, and distributes the message event in parallel to the slave brokers and the event stores. Each of the event stores store the message event in persistent storage, and notifies the master broker that the message event has been persisted. The master broker considers the message stabilized n a quorum of the event stores. As the master broker does not take action until a messaging event is stabilized, in the event of failover, a new master broker is able to re-construct a broker state of the old master with no loss of data.