Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
An Entity of Type: work, from Named Graph: http://dbpedia.org, within Data Space: dbpedia.org

A long-lived transaction is a transaction that spans multiple database transactions. The transaction is considered "long-lived" because its boundaries must, by necessity of business logic, extend past a single database transaction. A long-lived transaction can be thought of as a sequence of database transactions grouped to achieve a single atomic result. A common example is a multi-step sequence of requests and responses of an interaction with a user through a web client. A long-lived transaction creates challenges of concurrency control and scalability.

Property Value
dbo:abstract
  • A long-lived transaction is a transaction that spans multiple database transactions. The transaction is considered "long-lived" because its boundaries must, by necessity of business logic, extend past a single database transaction. A long-lived transaction can be thought of as a sequence of database transactions grouped to achieve a single atomic result. A common example is a multi-step sequence of requests and responses of an interaction with a user through a web client. A long-lived transaction creates challenges of concurrency control and scalability. A chief strategy in designing long-lived transactions is optimistic concurrency control with versioning. (en)
dbo:wikiPageID
  • 17866900 (xsd:integer)
dbo:wikiPageLength
  • 899 (xsd:nonNegativeInteger)
dbo:wikiPageRevisionID
  • 914202433 (xsd:integer)
dbo:wikiPageWikiLink
dbp:wikiPageUsesTemplate
dct:subject
gold:hypernym
rdf:type
rdfs:comment
  • A long-lived transaction is a transaction that spans multiple database transactions. The transaction is considered "long-lived" because its boundaries must, by necessity of business logic, extend past a single database transaction. A long-lived transaction can be thought of as a sequence of database transactions grouped to achieve a single atomic result. A common example is a multi-step sequence of requests and responses of an interaction with a user through a web client. A long-lived transaction creates challenges of concurrency control and scalability. (en)
rdfs:label
  • Long-lived transaction (en)
owl:sameAs
prov:wasDerivedFrom
foaf:isPrimaryTopicOf
is dbo:wikiPageWikiLink of
is foaf:primaryTopic of
Powered by OpenLink Virtuoso    This material is Open Knowledge     W3C Semantic Web Technology     This material is Open Knowledge    Valid XHTML + RDFa
This content was extracted from Wikipedia and is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License