We have a requirement to run an aggregation service within a number of things, this service will be used to aggregate data from a number of stream entries at midnight (local time zone) every night for the previous 24 hours.

A high number of the 45,000 assets are located on the CET time zone.

We do not feel it would be sensible to allow each service to be triggered simultaneously as the number of threads that would be spurned would almost certainly cause the platform to hang.

The questions:

Does ThingWorx have any internal mechanism to queue the execution of threads to avoid overload of the server.

If not, do you have any recommended method of implementing thread execution control on large number of things which is growing daily and are all in different time zones.