Tersus: Fewer Services = Better Performance

Fewer Services = Better PerformanceDate: Jul 10, 2008

When all processing is made on the client side, performance is much better, especially if you access the server through the internet.

Nevertheless, some things must be made on the server side (most notably reading from the database or writing into the database).

If you need to access the server, minimize the number of services under a non-service (i.e. a client side model). In general, any user action (mouse click or entering data) should invoke no more than one service (and preferably none).

Needless to say, avoid as much as possible repetitive services under a non-service. In the terminology of http://www.tersus.com/#Id=617, you should reduce the “Service Cardinality” of your modeling as much as possible.

Specifically, minimize the number of service required to initialize display elements:

Put the initialization process at the top level (view, dialog, pop-up, pop-in) so all initializations requiring server access can be made inside a single service. This might require re-use of initialization sub-processes for display elements that are re-used in various places (because you don't put the initialization of each display inside it).

Unless the overhead is marginal, initialize only information the user is going to see or is expected to see (e.g. not tabs that are not frequently accessed by the user, which can be initialized just-in-time when the user switches to them). See the discussion in http://www.tersus.com/#Id=1280.

When switching back to part of the display already visited, avoid re-initialization that requires server access (unless there is a reason to believe the underlying data has changed since the previous visit).

Reduce Network TrafficRecords, Rows or Table?Carefully Plan Database AccessSee Also:

To use the full functionality of this web site, JavaScript needs to be turned on.

For best results, use the Firefox browser..

Loading ...