Five things to know about IBM MessageSight
Christian Karasiewicz 270005XS4E Visits (6883)
This blog post is contributed by Nguyen Van Duy, an IBM Associate Certified IT Architect with GTS Vietnam, working for GBS Innovation Center as the development team leader in Vietnam.
The Internet is no longer a global network just for computers but is becoming an environment for diverse devices to join. Preluded by mobile, billions of smart devices are instrumenting our world today. They are controllers, sensors, meters, gauges, switches, scanners, radio frequency identification (RFID) and supervisory control and data acquisition (SCADA) systems and so on, which are addressable with network-connected embedded microprocessors. By 2020, the number of devices connected to the global network is expected to be 30 billion, according to ABI Research. Those devices are going to publish data, consume data or both, and they will need to responsively interact with each other and with applications through an appropriate protocol to perform tasks without human involvement.
Aside from the other two well-known messaging protocols—Advanced Message Queuing Protocol (AMQP) and Simple (or Streaming) Text Oriented Messaging Protocol (STOMP)—the Message Queue Telemetry Transport (MQTT) protocol seems to be a very good fit for this need because it's designed to be lightweight and less resource-consuming (network bandwidth, power) while also attempting to ensure reliability with some assurance of delivery.
Preparing for the emerging Internet of Things, in April 2013 IBM announced IBM MessageSight, which is a 2U appliance-based messaging server built on MQTT technology. MessageSight is optimized to address the massive scale requirements of the machine-to-machine (M2M) and mobile use cases and designed to handle and route a tremendous volume of messages among diverse types of devices reliably and securely.
Below are five key aspects of MessageSight and details on how the appliance could perform on each.
1. Scalability and performance
Built upon the MQTT messaging protocol, which is faster and requires less bandwidth and power than traditional HTTP(s), IBM MessageSight is well-suited with tags and sensors for mobile devices and other “things” that typically have low power and low communication bandwidth capabilities. Also, the high-scale, asynchronous publish/subscribe with event-oriented paradigm could provide responsive interaction, which turns into better user experience and better scalability.
If high availability (HA) and disaster recovery ability are required, two MessageSight appliances could be easily configured to an HA-enabled mode to act as an HA pair of nodes, one to be the primary node (the appliance that is processing messages) and the other to be the standby node (the appliance to which the primary node is replicated). With HA enabled, the messaging services can withstand an outage of an appliance and continue to provide messaging services.
There are three main aspects to security in MessageSight: transport level security, authentication and authorization.
4. Integration ability
As a full-featured messaging appliance, the ability to integrate with other systems is a key feature of IBM MessageSight.
Built on the open MQTT, MessageSight supports MQTT client applications and libraries for a variety of platforms such as:
If you want to play around with it to see how it works from a developer's perspective, you can quickly get a version of MessageSight developer here. It usually takes less than one hour to have everything set up and running and to start experiencing the virtual appliance.