Hello everyone 👋
I've been on holiday this week, so this will be a fairly quick update.
Of course while I'm away I like nothing more than to work! So I Spent a bit of time updating foundthings.com, which is now running in full on the network (DNS + Content distribution).
Setup was easy and it's pretty performant 🙂
As I mentioned last week, we've now added Edge-Device alongside Edge-Host in the headers returned by the network.
DEVICE_ID is the ID given to the device by Agent, the application that manages authentication and software updates. When Agent registers the device with Consul, it registers using this ID to create a Device service.
HOST_ID is the Consul ID for the host application. When Agent authenticates on the network it downloads Host and Host connects to Consul using the HOST_ID.
Why don't we have a single ID? Because each Consul service need a unique ID. It's important to know that if Host goes offline, the Agent application is still running.
For Telemetry it's also important to be able to distinguish between the resources used by Device Agent, and by Host.
I see the following network headers for foundthings.com:
Edge-Device => 9e82bf98-d6f7-4559-b91c-95c578eb74a2
Edge-Gateway => 455106e7-612e-411b-9ded-38bfce8f59ee
Edge-Host => 82a3ce68-d489-4fab-afed-7046e3988752+We also return some cache control headers:
Etag => "11ec4-wBAM3fVvut8jqaPsB2ab15I2Zng"
X-Cache => HITAside from this update to the network, the network team have been working on improving the performance of the Gateway HTTP request queue, and have also been building out the transfer queue for Edge Storage. The response time for requests has been reduced by around 40% on the back of this work.
Updates
Last Updated:
September 2019