Now that TCP/IP connections over WIFI or 3G/4G are practically everywhere, consumers are able to use a variety of machines and devices at any given time of day to access business applications. As this increase in "smart" devices expands with no end in sight, so does the large amount of data that needs to be processed and acted upon.
Earlier this year IBM announced MessageSight, an appliance-based messaging server that is optimized to address the massive scale requirements of machine to machine (m2m) and mobile user scenarios. The MessageSight appliance joins IBM's portfolio of middleware to help bridge backend enterprise environments to remote "smarter" clients as the planet becomes more digitally interconnected. This allows organizations to provide an interactive experience with their users and offers real-time data analytics of large data.
The IBM MessageSight appliance is designed to sit at the edge of the enterprise and can extend an existing messaging infrastructure or be used standalone. It allows a large number of clients to be concurrently connected, easing the load on backend systems. Demos have shown the appliance handling a million connections at once! Incorporating MessageSight into your mobile messaging solutions can provide high-speed Big Data analytics, driving millions of low-latency analytical decisions per second.
I've recently been part of a team to create a new IBM Redbooks publication that will demonstrate how to utilize IBM MessageSight with MQTT (MQ Telemetry Transport) for a mobile user experience. I'd like to share with you some of the features and capabilities of IBM MessageSight which make it a smart solution for the huge quantities of real-time event driven data that needs to be managed by applications in today's world.
The IBM MessageSight platform delivers performance and provides needed security features. This reliable, easy-to-deploy appliance has the capability to handle a million concurrent connections and process millions of messages per second. When I say "easy-to-deploy" it really has been shown to go from unpacking the box to up and running in less than 30 minutes in this YouTube video: http://www.youtube.com/watch?v=RZJbqWLj1Zc
MessageSight can be administered through a browser with the Web User Interface (Web UI). Most of the functions available in the Web UI are accessible with a Command Line Interface (CLI) as well.
With the versatile IBM MessageSight appliance, you can use either the MQTT protocol for low latency pub/sub (ideal for M2M) or Java™ Messaging Service (JMS) to transfer messages received from remote clients to backend applications. The diagram below shows some examples of how clients connected to the IBM MessageSight appliance can interface with WebSphere MQ and other backend applications.
In a previous blog entry "What is MQTT and how does it work with WebSphere MQ?" I discussed how MQTT (MQ Telemetry Transport) protocol can be used for pub/sub messaging and integrated with WebSphere MQ. The MQTT protocol is optimized for networks with limited processing capabilities, small memory capacities and high latency.
The advantage of using MQTT protocol instead of HTTP is that the MQTT protocol design minimizes network bandwidth requirements while sending data reliably. The benefits to consumers are reliability, less battery drain and lower data plan costs due to fewer bytes necessary for each messaging transaction. The MQTT header only requires 2 bytes!
HTTP is designed as a request-response protocol for client-server computing, not necessarily optimized for mobile and push capabilities, particularly in terms of battery usage. MQTT can be integrated with IBM Worklight allowing developers to create mobile applications. And the lightweight MQTT protocol allows publish/subscribe messaging to send data reliably to phone or tablet apps without having to code retry logic in the application.
The MQTT protocol's efficient use of network and battery power makes it compatible for an enterprise application when it needs to push data to one or more phone apps. MQTT helps overcome problems experienced by HTTP by offering reliable delivery over fragile networks. MQTT will deliver message data to the required Quality of Service (QoS) even across connection breaks.
Security is built into the core of the IBM MessageSight appliance. It is DMZ ready and provides many aspects of security including transport, connection, messaging, admin and MQ connectivity. SSL/TLS transport security can be configured. You can also require authentication by userid/password or by certificate. MessageSight connects to a Queue Manager as a client whereby security checks can be made to assign a specific ID to connections from the IP of the MessageSight appliance.
The bottom line: IBM MessageSight appliance provides an easy way to implement event driven architecture at the edge of the network. It can process messages with an unprecedented level of scale yet it is simple to use and administer.
I invite you to learn more about IBM MessageSight using the online Information Center and the development community on developerWorks. And check back for more MessageSight info at this blog site in the upcoming months!