Skip to main content

MessageSight

IBM MessageSight is a full-featured messaging appliance specifically designed for machine-to-machine (m2m) and mobile environments and is a central component of the IBM IoT cloud. IBM MessageSight is designed to handle high throughput messaging in various use cases and to handle concurrent connectivity among a large number of devices and applications, with predictable latency.

Our team contributed an extremely fast and efficient message-persistent mechanism that allows MessageSight to persist hundreds of thousands messages per second. In addition, we designed and developed the entire High Availability solution offered by the product.

  • - MessageSight as server
  • - MessageSight persistent message store
  • - MessageSight high availability
  • - MessageSight replication

    After the primary and standby nodes are physically connected and configured, the primary node continually replicates both the persistent store and the appliance configuration information to the standby node. If the primary node fails, the standby node has the latest data that is needed for applications to continue messaging services. The standby node does not accept connections from application clients or provide messaging services until a failover operation occurs, which is described in the next section.

  • - MessageSight failover

    If the standby node detects that the primary node failed or is unreachable, it performs failover processing by using information that was replicated from the primary node. Then, the standby acts as the primary node to continue messaging services. Applications that were connected to the original primary node can then connect to the standby node.

  • - MessageSight synchronization

    When a failed node is restarted and reconnected to the current primary node, the primary performs a synchronization operation to replicate persistent store and appliance configuration information from the primary, to be sure that the standby has the latest information to resume messaging services. After synchronization, the primary node will provide messaging services, and the standby will be ready to take over if the primary fails.