This is probably going to be a slightly open ended question, but I’m really just after examples of how people are building their web services around the Particle ecosystem.
My requirements I think are fairly typical of many potential enterprise users on here:
- Want to have customers who each have their own devices
- Want to log data from devices into a database, potentially take action on this data in certain situations
- Customers need to be able to view data via a dashboard
- Needs to be reasonably scalable
Up to this point I’ve been using simple authentication (as opposed to two-legged) and a static webpage displaying only live data.
I feel that this solution is probably too restrictive.
I see many potential solutions that have been talked about in these forums, some of which are the following:
Xively (seems expensive and a duplicate of much of the existing Particle infrastructure)
Ubidots (Haven’t much of chance to research but looks interesting)
PowerBi (Good solution for dashboards etc. but potentially too high-level)
AWS / Azure (Powerful if you know what you’re doing)
Heroku (Seems like a good choice, although bit of a learning curve if you haven’t used NodeJS before)
I think with some of the options there is a risk of trying to write too little code and just linking up multiple services to do all the work for you, ending up with something quite expensive at scale and not overly flexible.
I think AWS sounds like an interesting idea, with quite a powerful IoT platform, but at scale (assuming webhooks, as TLS via AWS doesn’t really sound like an option yet) is it going to be prohibitively expensive paying for both Particle and AWS-IoT?
In terms of simple vs two-legged authentication - do we really need two-legged authentication for customer data storage? If data is not sensitive, can it just be stored e.g. in a dynamoDB table using the device ID as it’s identifier and retrieved via a static webpage?
I’ve read this tutorial https://mlapida.com/thoughts/serverless-iot-with-particle-and-aws
Which is very interesting however I fear that having ‘serverless IoT’ when actually dealing with multiple customers who are being added/removed continuously isn’t quite as simple as setting up a couple of AWS services.
Sorry this has been a bit disjointed but keen to hear any thoughts. @RWB I understand you’ve got a solution with webhooks + Azure + PowerBi. How is this working for you? Do you still use simple auth or are you running your own server to store customer accounts?
In summary, I’m not opposed to learning and writing some code, I just want to make sure I make an informed decision before diving into a particular platform.