Somewhat interesting and will keep an eye on it, but the "current ecosystem" paragraph seems to both miss some options and confuse some things. E.g. yocto isn't an update solution, but is presented as contrast to some options for bigger systems, and no of the more advanced competitors for updates, both software and services, aren't mentioned at all - but those are what you need to convince me you're better as. (And yes, the space certainly can use some more options trying new things!)
True, Yocto is not technically an update solution! We explained it as such to try and keep our post a little shorter, but perhaps we oversimplified a bit too much there. What we probably meant to say is "the Yocto ecosystem".
We mention Yocto and internal tooling rather than other competitors because they're what we hear most often. We would have loved to include more discussion about why were better than other solutions, but it would have made our post a little unwieldy.
It'd be great to hear a comparison of when you'd want to use Deviceplane vs something like mender.io or updatehub.io. I'm a great fan of the A/B dual image update strategy because it's simple, atomic and resilient to errors or loss of power during an update. Does Deviceplane still provide some of those assurances or would I want to use Deviceplane in conjunction with something like Mender?
I deploy updates on IoT devices that are unattended and can only afford minimal downtime. If an interrupted update (due to loss of network connectivity or power) caused a device to be unreachable/unupdateable it would be bad. I'd also be concerned with using DevicePlane as it's presented because I'd have no way of updating the device's kernel version that I first deploy with.
