Coding Best Practice for a dashboard / 1 User application

You can think of it this way:

Every service call is a return trip to the Server which can impact time to load.

So you want to carefully think about how you do your calls, can you get more information up front in one call without it going stale and use selected row.

Also in your services you want to reduce 'redundant information retrieval' as much as possible.

For example, if one query asks for a detailed set of records but then you also have a service asking for aggregates  can you somehow do that in one service?

If you want to dive a little deeper you can read this: https://community.ptc.com/t5/IoT-Tech-Tips/Designing-for-Scale-Events-and-Data-Handling/m-p/598761#M1278

Hello @gch,

Here's my personal opinion, I'm not writing those best practices, but this is how I interpret them.

It really depends on what those services do. Consider an example:

Example 1: A mashup displays a history of voltage readings + the average value for the last 24 hours.

Situation 1.1: You have two services -- GetHistoricData (feeds the grid) and GetAverageVoltage (for the value display). Both of those services have to do a database query for voltage readings.

Situation 1.2: You have a single service -- GetHistoricDataWithAverage, which returns an infotable with the embedded infotable and an average value, which you then bind to different widgets in your mashup. This service does only one query in the database.

Example 2: A mashup displays a history of voltage readings + the current state of the voltmeter (online / offline). In this case it doesn't make sense to merge two services in one, because you would have to do two queries anyway (the types of data are unrelated).

So the reason why reducing the number of service calls is a best practice is not because it saves time on HTTP processing -- those figures are often negligible compared to delays on the server AND within the mashup, as it renders in client's browser. Instead, the rationale is to avoid repeating the same (or similar) queries multiple times for loading one mashup -- that's the main performance killer in this context.

Now, back to your original question of whether it makes sense to optimize it for one single user... I guess it would be hard to justify even paying for ThingWorx license + your development effort for the 1-user app (or this user must be a pretty important person). I'm just trying to say that even if today you have an app like this, tomorrow most probably somebody will either add more users to it, or host some additional app there, and so the performance will suddenly become a major concern. So it's better to think about it ahead of time.

Regards,
Constantine