- 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.
推薦閱讀
- Hands-On Internet of Things with MQTT
- 計算機應用
- Mastering Salesforce CRM Administration
- Hands-On Cybersecurity with Blockchain
- Hadoop Real-World Solutions Cookbook(Second Edition)
- 機器人創新實訓教程
- Associations and Correlations
- 運動控制器與交流伺服系統的調試和應用
- 基于32位ColdFire構建嵌入式系統
- 基于單片機的嵌入式工程開發詳解
- 單片機技術項目化原理與實訓
- 強化學習
- Hands-On Business Intelligence with Qlik Sense
- 巧學活用Photoshop
- 百度智能小程序:AI賦能新機遇