Hi Tim,

Yes, you’re correct, the db is MySQL. There are currently two tables – Radu explains;

t1) devices
Has a single row / uRADMonitor detector, the primary key is the device id. It holds only the latest readings, the 24h average for radiation (as CPM) , the detected location, the overridden location , country code and offline/online status (considered offline if no data received for more than 10minutes).
As we speak this has 116rows and uses a little over 12KB.

t2) uradmonitor
This now has 7,4 million rows and a size of 432MB.
Each unit in the network sends data via a HTTP Get call to the data.uradmonitor.com . The parameters include the unit ID, measurements and a CRC. All this data gets into the database.
So each minute, one station send aprox. 58Bytes of data to the server.
The problem is we got quickly from one unit to ten, and we are now approaching 100 units.

When I mentioned replication I was thinking of doing it at the software level, some sort of ETL task to shuffle the data around and keep all the server/db’s in sync – but Radu suggested (I think) that the units themselves send their data to multiple servers. There would be some duplication of network traffic, but definitely a cleaner option.