To cover all the phases involved in your DPS development, you can use the following environments, each one with a specific purpose.
| Develop | Staging | Production |
|---|---|---|
|
This environment is used to design your DPS.
|
This environment uses the same configuration as per Production, but with sample data (Customer, Partners, Products). | This environment is used to publish the DPS to all your customers. |
|
Here you can make changes, configure, and test all the features without breaking anything which is visible by your customers. |
Here you can test in advance the configuration you are going to put in production, and thus accessible to your customers. | |
DPS application limits
According to the target environment, these are limits applied to the DPS in terms of number of business objects (e.g. Customers, Things) you can create, Data Points publishing rate, and API request rate.
| Develop | Staging | Production | |
|---|---|---|---|
| Max Users | 10 | 20 | No limits |
| Max Organization | 3 | 3 | No limits |
| Max Partners | 5 | 5 | No limits |
| Max Customers | 10 | 10 | No limits |
| Max Things | 50 | 50 | No limits |
|
Max API Calls |
60/min | 600/min | 600/min |
|
Max Data Points / Hour per Thing |
3600/hour | 10800/hour | 10800/hour |
Data Points per Hour indicates the maximum number of data points the remote product can publish to the IoT Connector channel every hour. For more details see the Publishing Rate Limit article.
Comments
0 comments
Please sign in to leave a comment.