Optimistic concurrency control: Difference between revisions

Revision as of 22:39, 5 February 2024

Revision as of 23:51, 5 February 2024

Line 29:

* [[Google App Engine]] data store uses OCC.<ref>{{cite web | url = http://code.google.com/appengine/docs/whatisgoogleappengine.html | title = The Datastore | work = What Is Google App Engine? | date = 27 August 2010}}</ref>

* The [[Apache Solr]] search engine supports OCC via the _version_ field.<ref>{{cite web|url=https://lucene.apache.org/solr/guide/6_6/updating-parts-of-documents.html|title=Updating Parts of Documents|access-date=2018-06-28}}</ref>

* The [[Elasticsearch]] search engine supportsupdates OCCits documents via OCC. Each version of a document is assigned a sequence number, and newer versions receive higher sequence numbers. As changes to a document arrive asynchronously, the software can use the sequence number to avoid overriding a newer version attributewith an old one.<ref>{{cite web | urltitle=Optimistic concurrency control | website=Elastic http| url=https://www.elastic.co/guide/en/elasticsearch/reference/current/docsoptimistic-index_concurrency-control.html#index-versioning | title = Elasticsearch access- Guide - Index API | work = Elasticsearch Guide | date = 22 March 20122024-02-05}}</ref>

* [[CouchDB]] implements OCC through document revisions.<ref>{{cite web | url = https://wiki.apache.org/couchdb/Document_revisions | title = Couchdb Wiki - Document_revisions| archive-url = https://web.archive.org/web/20170204203059/https://wiki.apache.org/couchdb/Document_revisions | archive-date = 4 February 2017}}</ref>

* The [[MonetDB]] [[Column-oriented DBMS|column-oriented]] [[database management system]]'s transaction management scheme is based on OCC.<ref>{{cite web | url = http://www.monetdb.org/Documentation/Manuals/SQLreference/Transactions | title = Transactions - MonetDB | date = 16 January 2013}}</ref>