Following up with what Michael Laing wrote:
> Hmmm - we are in the early stages of adding MQTT to the NYTimes fabrik.
We are also in the early stages of adding MQTT to our campus-wide building automation supervisory system (about 12,000 devices and a little less than a million points).
> MQTT provides a standard paradigm that may relieve us of some technical debt and extend our service to more endpoints - and make it easier to add some new capabilities to the fabrik.
Exactly the same here (more specifically MQTT-SS), we need to provide a communications platform that makes it easier to build fault detention and diagnostic software, as well as a micro scale smart grid.
> The current fabrik supports the capabilities of MQTT for endpoints, but using our own semantics and code.
It would be nice if there was a standard for the data portion of messages, and until there is a better consensus, we'll be using BACnet binary encoding.
> We run a meshed, autoscaling AMQP backbone using RabbitMQ in multiple AWS regions and zones. The persistence layer is Cassandra.
Good to know I'm not completely off my rocker for going in the same direction, thank you! Our persistence layer will be Redis, we already have an existing database for trend data.
> The retail layer is over WebSocket/SockJS. We only have millions of users and many millions of messages - so not facebook scale...
We have no users, and not so many messages yet :-).
> Not even near production - shooting for mid-2015. Hope the boss agrees... :)
Building Automation and Control Systems Integration