
Registered since September 28th, 2017
Has a total of 4281 bookmarks.
Showing top Tags within 3 bookmarks
howto information development guide reference administration design website software solution service online product business uk tool company linux code server system application web list video marine create data experience tutorial description explanation learn technology build article blog world boat project download windows lookup security free performance javascript technical london control network beautiful tools support course file research purchase image library programming youtube example php construction opensource install community html quality profile computer feature power browser music platform mobile process work manage professional user share database hardware buy industry internet dance advice developer installation camera search 3d access customer material travel money test standard develop css review documentation engineering photography engine webdesign digital device speed api source event question management program client phone discussion story simple content water marketing app yacht account setup idea interface package fast communication cheap compare script market study easy live google resource operation demonstration startup monitor
Tag selected: distributed rdbms.
Looking up distributed rdbms tag. Showing 3 results. Clear
Saved by uncleflo on January 27th, 2017.
In transaction processing, databases, and computer networking, the two-phase commit protocol (2PC) is a type of atomic commitment protocol (ACP). It is a distributed algorithm that coordinates all the processes that participate in a distributed atomic transaction on whether to commit or abort (roll back) the transaction (it is a specialized type of consensus protocol). The protocol achieves its goal even in many cases of temporary system failure (involving either process, network node, communication, etc. failures), and is thus widely used.[1][2][3] However, it is not resilient to all possible failure configurations, and in rare cases, user (e.g., a system's administrator) intervention is needed to remedy an outcome. To accommodate recovery from failure (automatic in most cases) the protocol's participants use logging of the protocol's states. Log records, which are typically slow to generate but survive failures, are used by the protocol's recovery procedures. Many protocol variants exist that primarily differ in logging strategies and recovery mechanisms. Though usually intended to be used infrequently, recovery procedures compose a substantial portion of the protocol, due to many possible failure scenarios to be considered and supported by the protocol.
distributed rdbms transaction theory explanation administration wikipedia article howto protocol business service inter-service algorithm
Saved by uncleflo on January 27th, 2017.
The typical example of a transaction involves Alice and Bob, and their bank. Alice pays Bob $100, and the bank needs to debit Alice and credit Bob. Easy enough, provided the server doesn't crash. But what happens if the bank debits Alice, and then before crediting Bob, the server goes down? Or what if they credit Bob first, and then try to debit Alice only to find she doesn't have enough funds? A transaction allows the debit and credit operations to happen as a package ("atomically" is the word commonly used), so either both operations happen or neither happens, even if the server crashes halfway through the transaction. That way the bank never credits Bob without debiting Alice, or vice versa.
database opensource postgres distributed distributed rdbms transaction blog article explanation guide howto administration development commit inter-service
Saved by uncleflo on October 12th, 2016.
Crate is an open source, highly scalable, shared-nothing distributed SQL database. Crate offers the scalability and performance of a modern No-SQL database with the power of Standard SQL. Crate’s distributed SQL query engine lets you use the same syntax that already exists in your applications or integrations, and have queries seamlessly executed across the crate cluster, including any aggregations, if needed. Crate is masterless and simple to install, operate and use. It handles transactional and analytical needs in one single database. Crate has been designed from the ground up to support the huge scale of Web, mobile and IoT applications. Love containers? Crate runs perfectly as stateful container.
crate distributed rdbms high-availability partition data dbms rdbms availability performance upscale scalability sql transaction storage engine website administration server software solution product opensource
No further bookmarks found.