Jump to content

Transaction server

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Alvestrand (talk | contribs) at 22:45, 23 December 2006 (Labels & links - needs cleanup; important concept, but badly described.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Linkless

A transaction server is a software component that is used in implementing transactions.

A transaction involves multiple parts which must be completed atomically, for example when paying someone from your bank the system must guarantee that the money is taken from your account and paid into the other persons account. It would simply be unacceptable for just one or the other action to take place.

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", 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 comprise 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).

See also Transaction processing