I’d like to set up three fully separate “systems”, each of which containing a bunch of devices, running the same code but in different versions, and cloud apps.
- The “development” system. That’s where developers (device and cloud) run the most recent builds and everything is moving fast and generally broken …
- The “beta” system. That’s where friendly users use devices and cloud software that’s not entirely polished and may have bugs
- The “production” system. Real customers pay real money to use the system, and it better work.
I’m trying to map this into the concepts provided by the Particle console etc. For each of these systems, I want a fully separate message broker (no accidental polluting of customers with development bugs). How would I best do that? Does what Particle calls a Product create a separate name space on the message broker, and I would consider dev / beta / production separate products? Or should I use three different Particle accounts?
Also, from a security perspective, lots of developers should have access to “development” but only very few people should have access to “production”.
Any advice on how to manage this is appreciated …