The second step in your analysis is to decide whether your
data needs lend themselves to a distributed relational database solution.
Applications where most database processing is done locally and
access to remote data is needed only occasionally are typically good candidates
for a distributed relational database.
Applications with the following requirements are usually poor candidates
for a distributed relational database:
- The data is kept at a central site and most of the work that a
remote user needs to do is at the central site.
- Consistently high performance, especially consistently fast response time,
is needed. It takes longer to move data across a network.
- Consistently high availability, especially twenty-four hour, seven-day-a-week
availability, is needed. Networks involve more systems and more in-between
components, such as communications lines and communications controllers, which
increases the chance of breakdowns.
- A distributed relational database function that you need is not currently
available or announced.