- Fri Oct 02, 2020 8:31 am
#88994
You can truly write your message payloads in any format, and then translate into other formats as needed, but using JSON like I did means that the cloud vendor supplied tools will unpack it for you as it arrives and let you graph it etc.
The down side is the messages are longer than if you used a binary format - for instance you can squeeze most sensor readings into a single byte if you work out an average value as a fixed zero point, calculate the offset from that average, and you can store in 8 bits with 1 or 2 bits as the fractional portion
eriksl wrote:So if I would this format (which seems quite logical to me) at least multiple services would be able to process it (either directly or with a translation step)?
You can truly write your message payloads in any format, and then translate into other formats as needed, but using JSON like I did means that the cloud vendor supplied tools will unpack it for you as it arrives and let you graph it etc.
The down side is the messages are longer than if you used a binary format - for instance you can squeeze most sensor readings into a single byte if you work out an average value as a fixed zero point, calculate the offset from that average, and you can store in 8 bits with 1 or 2 bits as the fractional portion
