Client Server Application Design
| Client Server Application Design | ||||||||||
|
Although it is possible to run the applications on the same server as the database, once the database starts to grow it if often wise to move the applications to another machine. The decision to move the application should be based on CPU usage and the memory statistics. The major bottlenecks on client/server systems is the network and there are a number of areas that should be examined within the application design that reduce this overhead.
If the database server has a number of 'hot' areas consider grouping these tables together and move them to different machines. This should ensure the load is balanced across two or more systems. | ||||||||||
| Shared Memory or TCP/IP connection | ||||||||||
|
There are two fundamental methods of connecting to the server, either shared memory or tcp/ip. The fastest connection type is shared memory as the messages are placed in and read from memory via the ipc sub-system. But the shared memory segment is not secure as any user can attach to the segment and view or modify the data within it. Therefore, if a secure mechanism is required the tcp/ip connections should be used. |
