Some simple criteria are presented shortly to assist in the task of selecting styles. However, following this single guideline will greatly simplify the whole process:
Always design applications to be modular and flexible.
By maintaining a clear distinction between the four elements of presentation logic, user task support, business rules, and data manipulation logic, you will be in a good position to change between client/server styles as needed. This can be very useful because it is difficult to fully anticipate the behavior of an application before it is actually executing. If you designed an application to run as a remote data access application and discover after implementation that the distributed process style would perform better, it is relatively easy (with CA Gen) to move the data manipulation logic from client to server.
In the CA Gen environment, the appropriate level of modularization is generally achieved by ensuring that the procedure step logic (usually associated with presentation) is held separate from elementary process logic.
Use remote data whenever you can, for example, when you are:
This is the easiest style to use because it relies on the DBMS to perform the remote access. There is no division of application components involved.
However, with this style, performance may not be optimum, and data integrity can be compromised.
|
Copyright © 2013 CA.
All rights reserved.
|
|