- Implementing Azure Cloud Design Patterns
- Oliver Michalski Stefano Demiliani
- 176字
- 2021-06-30 19:31:53
Concurrency and consistency
Let's start with the term concurrency. Here, you have to answer the following question: What kind of concurrency mechanism do you want to use?
The following options are available:
- Pessimistic concurrency control: In the case of pessimistic concurrency control, the application performs many updates, which can contain a high conflict potential. The mechanism you choose will try to counteract this with record locking.
- Optimistic concurrency control: In the case of optimistic concurrency control, there is no high conflict potential. Therefore, this mechanism provides only a simple timestamp lock.
The next term is consistency or rather, consistency model.
Consistency models are used in distributed systems or distributed data stores (such as a filesystem or a database). The consistency model specifies a contract between user and system, wherein the system guarantees that if the user follows the contract, the memory will be consistent and the results of memory operations will be predictable.
I will address the topic of the consistency model later in this chapter, in the description of the Azure Cosmos DB.
推薦閱讀
- Security Automation with Ansible 2
- 智能工業(yè)報警系統(tǒng)
- PyTorch Deep Learning Hands-On
- RedHat Linux用戶基礎(chǔ)
- 空間機械臂建模、規(guī)劃與控制
- INSTANT Heat Maps in R:How-to
- Linux內(nèi)核精析
- 從零開始學(xué)Java Web開發(fā)
- IBM? SmartCloud? Essentials
- 貫通開源Web圖形與報表技術(shù)全集
- AVR單片機C語言程序設(shè)計實例精粹
- 探索中國物聯(lián)網(wǎng)之路
- Building Impressive Presentations with Impress.js
- 單片機原理、應(yīng)用與仿真
- 機器人制作入門(第3版)