DBpedia – Linked Data Fragments

Matches in DBpedia 2016-04 for { <http://wikidata.dbpedia.org/resource/Q5283142> ?p ?o }

• Q5283142 subject Q5898411.
• Q5283142 subject Q7011992.
• Q5283142 subject Q7285247.
• Q5283142 subject Q7352018.
• Q5283142 subject Q7464929.
• Q5283142 abstract "Distributed concurrency control is the concurrency control of a system distributed over a computer network (Bernstein et al. 1987, Weikum and Vossen 2001). In database systems and transaction processing (transaction management) distributed concurrency control refers primarily to the concurrency control of a distributed database. It also refers to the concurrency control in a multidatabase (and other multi-transactional object) environment (e.g., federated database, grid computing, and cloud computing environments. A major goal for distributed concurrency control is distributed serializability (or global serializability for multidatabase systems). Distributed concurrency control poses special challenges beyond centralized one, primarily due to communication and computer latency. It often requires special techniques, like distributed lock manager over fast computer networks with low latency, like switched fabric (e.g., InfiniBand). commitment ordering (or commit ordering) is a general serializability technique that achieves distributed serializability (and global serializability in particular) effectively on a large scale, without concurrency control information distribution (e.g., local precedence relations, locks, timestamps, or tickets), and thus without performance penalties that are typical to other serializability techniques (Raz 1992).The most common distributed concurrency control technique is strong strict two-phase locking (SS2PL, also named rigorousness), which is also a common centralized concurrency control technique. SS2PL provides both the serializability, strictness, and commitment ordering properties. Strictness, a special case of recoverability, is utilized for effective recovery from failure, and commitment ordering allows participating in a general solution for global serializability. For large-scale distribution and complex transactions, distributed locking's typical heavy performance penalty (due to delays, latency) can be saved by using the atomic commitment protocol, which is needed in a distributed database for (distributed) transactions' atomicity (e.g., two-phase commit, or a simpler one in a reliable system), together with some local commitment ordering variant (e.g., local SS2PL) instead of distributed locking, to achieve global serializability in the entire system. All the commitment ordering theoretical results are applicable whenever atomic commitment is utilized over partitioned, distributed recoverable (transactional) data, including automatic distributed deadlock resolution. Such technique can be utilized also for a large-scale parallel database, where a single large database, residing on many nodes and using a distributed lock manager, is replaced with a (homogeneous) multidatabase, comprising many relatively small databases (loosely defined; any process that supports transactions over partitioned data and participates in atomic commitment complies), fitting each into a single node, and using commitment ordering (e.g., SS2PL, strict CO) together with some appropriate atomic commitment protocol (without using a distributed lock manager).".
• Q5283142 wikiPageExternalLink ccontrol.aspx.
• Q5283142 wikiPageExternalLink description.
• Q5283142 wikiPageExternalLink Raz92.html.
• Q5283142 wikiPageWikiLink Q1067690.
• Q5283142 wikiPageWikiLink Q1202008.
• Q5283142 wikiPageWikiLink Q1301371.
• Q5283142 wikiPageWikiLink Q137712.
• Q5283142 wikiPageWikiLink Q1771903.
• Q5283142 wikiPageWikiLink Q180634.
• Q5283142 wikiPageWikiLink Q2051600.
• Q5283142 wikiPageWikiLink Q2290484.
• Q5283142 wikiPageWikiLink Q249999.
• Q5283142 wikiPageWikiLink Q2914952.
• Q5283142 wikiPageWikiLink Q3306359.
• Q5283142 wikiPageWikiLink Q483639.
• Q5283142 wikiPageWikiLink Q5152903.
• Q5283142 wikiPageWikiLink Q5283161.
• Q5283142 wikiPageWikiLink Q5570820.
• Q5283142 wikiPageWikiLink Q5570890.
• Q5283142 wikiPageWikiLink Q5898411.
• Q5283142 wikiPageWikiLink Q690079.
• Q5283142 wikiPageWikiLink Q7011992.
• Q5283142 wikiPageWikiLink Q7181706.
• Q5283142 wikiPageWikiLink Q727512.
• Q5283142 wikiPageWikiLink Q7285247.
• Q5283142 wikiPageWikiLink Q7352018.
• Q5283142 wikiPageWikiLink Q7464929.
• Q5283142 wikiPageWikiLink Q83571.
• Q5283142 wikiPageWikiLink Q844565.
• Q5283142 wikiPageWikiLink Q8513.
• Q5283142 wikiPageWikiLink Q922437.
• Q5283142 wikiPageWikiLink Q92988.
• Q5283142 wikiPageWikiLink Q989016.
• Q5283142 comment "Distributed concurrency control is the concurrency control of a system distributed over a computer network (Bernstein et al. 1987, Weikum and Vossen 2001). In database systems and transaction processing (transaction management) distributed concurrency control refers primarily to the concurrency control of a distributed database.".
• Q5283142 label "Distributed concurrency control".