Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mosquitto-dev] Cassandra as a retained message store

Michael,

I would definitely be interested in hearing updates from you, especially the solution around query. I think your use case is what a lot of other people will have too so it would be good to share experiences. It will also be interesting to see the different approaches people take to the query of MQTT messages.

 

Ian

 

 

 

 

From: mosquitto-dev-bounces@xxxxxxxxxxx [mailto:mosquitto-dev-bounces@xxxxxxxxxxx] On Behalf Of Laing, Michael
Sent: November-26-14 10:24 AM
To: mosquitto-dev@xxxxxxxxxxx
Subject: [mosquitto-dev] Cassandra as a retained message store

 

I am experimenting with MQTT as a way to extend the nytfabrik at the edge, complementing and perhaps replacing our custom WebSocket/SockJS protocol.

 

We use RabbitMQ with topic routing on the nytfabrik global backbone mesh, so we are familiar with wildcarding, subscription, etc.

 

And we have lots of 'retained' messages - 10's of millions growing to 100's of millions.

 

This is no problem for Cassandra but, as we look to support MQTT, we need a technical solution for query with wildcards on retained messages.

 

Cassandra has a limited query language but can be very fast. I was looking for a way to run 'close to the metal' (no additional layers) and now have a working prototype architecture and algorithms for store and query that are simple, fast and which scale. So I think that technical blocker is overcome for our usage cases.

 

Anyway, if this is of interest, I'll keep this list informed, and maybe solicit some advice.

 

We're not sure yet how we'll add MQTT to the nytfabrik, but most likely we would remix mosquitto with our own code, package it up, and run it under python on our autoscaling edge instances.

 

Cheers,

 

Michael


Back to the top