Actions
Engagement
  • Author Author: cstanton
  • Date Created: Date Created
  • Last Updated Last Updated:
  • Views 1135 views
  • Likes 1 like
  • Comments 17 comments
Related
Recommended

What puts you off about IoT Services?

There's AWS, Google, adafruit.io - what makes you roll your own or not use these services, or do you use these services? Add a comment below.

Parents Comment Children
  • in reply to BigG

    Actually, what I said is strictly true "the risk of the cloud provider simply pulling the plug, leaving you with a(n almost) useless piece of hardware is very real". You might argue whether that risk materialised or not in the case of the Particle Mesh (i.e. whether the devices became useless, almost useless or still useful as a Circuit Python device) but the risk is very real. That is why Microsoft decided to guarantee that the Azure Sphere platform would remain supported for a specified number of years.

  • in reply to stevesmythe

    Ah I had misread. I had assumed you were referring just to the Mesh devices. Yes that is a very real risk indeed with cloud service provisioned devices. Electric Imp would be another candidate having this risk.

     

    However, I believe with Particle you still have a work around with all their devices as I believe (but I could be mistaken) that they have documented alternatives for all hardware, should you need to reflash the device. So you can at least put in your own cloud service on their hardware at any stage. Not many cloud providers do that with their devices. In terms of ease of use, Particle still tops it, my opinion. Azure Sphere has too much IT methodology written into it, which isn't always suited for embedded environments IMHO.