Jump to content

Atomicity (database systems)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Gdimitr (talk | contribs) at 02:36, 21 November 2003. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Atomicity in the context of concurrency control

Atomicity - either all or no operations are completed. See concurrent programming

Atomicity in the Component Based Paradigm context

Atomicity is an element of orthogonality guaranteeing hermetic interfaces among components of a component-based system. This avoids that malfunctions in one component would result into side-effects in another. In addition it guarantees that services provided by a component are either offered as a whole, or not at all. Systems build according to this design principle localise the side-effects of changes within the module that such change was manifested. Changes affect the emergent behaviour of such a system only if their technical effect is explicitly described by the formal definition of its logic.