Hi @MA8731174
Polling a ThingWorx service every 10 seconds can be acceptable for lightweight services that return a single property value, especially if there are no database queries, file access, or loops involved. However, there are several considerations regarding performance, scalability, and platform load:
Performance Impact: While the service is lightweight, frequent polling can still add up, especially if multiple clients are making similar requests. It's essential to monitor the overall load on the ThingWorx platform to ensure it can handle the cumulative requests without degradation in performance.
Scalability Concerns: If the number of clients increases or if the polling frequency is reduced, the load on the platform could become significant. It's advisable to assess the expected growth in client connections and adjust the polling strategy accordingly.
Best Practices: To optimize performance and reduce potential issues, consider implementing strategies such as:
- Using event-driven architecture or webhooks instead of polling, if applicable.
- Caching results where possible to minimize repeated calls for the same data.
- Monitoring service execution times and memory usage to identify any bottlenecks.
For further insights and best practices, you can refer to the following resources:
Regards.
--Sharon