Overview

Meshblu aims to be a cross-protocol M2M platform. Meshblu 1.0 made that possible, however it was difficult and time consuming to support additional Protocols. Every Protocol Adapter was required to re-implement much of the logic that made Meshblu function. This caused defects, diverging implementations, and many other undesirable issues.

Horizontal scalability was also challenging due to the implementation of socket.io and messaging. Great strides were made to improve the messaging layer in Meshblu 1.0; yet there was still more to be done.

Meshblu 2.0 makes it easy to implement a Protocol Adapter quickly, with minimal code. Meshblu Core contains all database access logic and message routing/delivery. The Protocol Adapter interfaces with Meshblu Core and the client.

Meshblu 2.0 is split into two major functions, Job and Message.

In order to maximize performance each Job is placed into a work queue that is managed by the Dispatcher. While most of Meshblu 2.0 is currently implemented in Node.js, it is no longer strictly limited to Node.js. A Protocol Adapter may be implemented in any language as long as it adheres to the Request/Response specification.