Page History

...

• Many of the old DP rules about benchmarking and load testing, etc. seem to have been lost in the scramble for client/server applications.
• The old rules still do apply. If you ignore them until your application is complete then you are taking a large risk.
• Building client/server applications and using client/server tools may place a great deal more load on your LAN and twinax communication subsystems. Can they handle this increased load?

To Summarize:

• Spend a lot of time in design
• Use virtual fields to do dynamic "joins"
• Use triggers
• Put validation rules into the Repository and I/O Modules
• Distribute load/logic across the Client and Server
• Avoid pushing too much data through communication subsystems
• Do realistic tests/benchmarks before implementation
• Note that the amount of data transferred includes not just data from the database on the Server to the Client program but also from the Client program to the UIM (User Interface Manager).

This is very important and often overlooked.