12.

DATABASE SYSTEM ARCHITECTURE

Server System Architectures,

transaction server and data servers

Transaction server
A transaction involves multiple steps which must be completed atomically, as though it is
a single operation which can not be interrupted, even though it may require multiple
steps. For example, a bank moving money from account A to account B must remove it
from A and also add it to B; it would be unacceptable to do only one of these steps. If the
server is unable to accomplish all of the steps it must be sure to perform none of them.
This will mean ensuring that transactions are guaranteed, or that if a transaction fails the
system can tell this has happened.

In the case of a transaction failing it can then be "backed out" (or "rolled back"), which
will mean that the system reverses all the actions that happened during the partial
completion of the transaction. This is sometimes referred to as the ACID property.

A transaction server will consist of a system providing the safety described above, and an
environment where programs can be written to make use of these features. It will also
have various connection protocols to allow it to connect to the databases involved, and to
the front end software (for example the computer of a telesales person or the web
interface of an online bank).

Parallel Systems,
a) troughput
b) response time
1) Spped-up and scale up
2) Interconnection network architectures
3) Parallel database architures
a) shared memory
b) shared disk
c) shared nothing
d) hierachical

Distributed Systems,
1. homogeneous distributed databes
2. heterogeneous distributed databases.

Network Types.