Each reporting system / products does its own reporting, and no plans of adding ELK integration right now, although we are moving to the ELK stack so it might happen.
We think of it more as a database++ with financial primitives baked in, so we want to keep it very simple and dumb. It’s not a complete solution - it’s a book to write in, and you need another service that decides what and how to write and writes it (we call it the bank or teller service, and it’s all business logic for our business). Each product has its own bank to teller service, but they all use the same ledger underneath.
I prefer having the REST API running on a raspberry pi or a local server, that can proxy things to Google Cloud and back, just because in case something happens to the internet connection, your house is bricked, by having a local instance your system does not rely on your ISP for speed and availability.
I'd be curious of how do you update these devices, did you get OTA to work through an nRF24? did you need some external eeprom for that?
I agree, and I think the author should write a blog-post/tutorial about it, it might be useful for a lot of people that are looking into blockchain/ethereum/solidity, me being one of them.
The RAM and CPU usage is interesting, I think most of the people hate electron apps for their thirst of resources.
Just by looking at the activity monitor I'm curious what's the emptyWindow process.