Vizier87
Active Member
Hi guys,
I've been designing a door lock system which sends GET requests using the ESP8266 for writing and reading via the API from Thingspeak. I'm planning on using a single channel to cater for a few door locks.
Currently it seems manageable.
My concern is that, let's say the number of devices are a lot (let's say they get to more than a 100), then this would probably mean the IoT device would have to make "read" requests up to a few fields, since there might be more than a few people using their door locks at a time.
I'm thinking in the long run, maybe each door lock ought to have it's own channel? Is this usually the practice?
And if this is the case, what are other cheaper middleware options should I explore?
Thanks!
I've been designing a door lock system which sends GET requests using the ESP8266 for writing and reading via the API from Thingspeak. I'm planning on using a single channel to cater for a few door locks.
Currently it seems manageable.
My concern is that, let's say the number of devices are a lot (let's say they get to more than a 100), then this would probably mean the IoT device would have to make "read" requests up to a few fields, since there might be more than a few people using their door locks at a time.
I'm thinking in the long run, maybe each door lock ought to have it's own channel? Is this usually the practice?
And if this is the case, what are other cheaper middleware options should I explore?
Thanks!