# Percolator case study (Continue...)

+ pros
  + Simple to implement
  + Interbank transaction are realized on the basis of transaction based on a single row
  + Decentralized lock management
+ shortcomings
  + Need to manage centralized version numbers
  + Interact more on the network
------------------------------------------------------------
To summarize:
At this time, we found that the primary lock is actually a state bit of a thing. This state represents the current state of the thing in a table, so that we can implement the integrity of distributed transactions through the transaction integrity of a single node and a single row. Percolate is a simple way to implement. It implements cross-row transaction and decentralization lock management based on single-row transaction in BigTable.
The downside is that it requires an incremental version number management, and there is a lot of network interaction, and a certain delay cost.

- Advantages
  - Easy
  - Interrow transactions are implemented on the basis transaction single-row transaction in BigTable.
  - Decentralized lock management
- Disadvantages
  - Need centralized version number management
  - Multiple network interactions