PEER TO PEER SYSTEM FOR COLLABORATIVE WORK Using version control and fixed merge pattern to ensure eventual consistency
This paper addresses the possibility of using version control and fixed merge pattern to ensure eventual consistency for collaborative work tools. Where the version control is upheld by a vector clock and used to detect conflicts. Which in turn are solved by rolling back to the last common versi...
| Main Author: | |
|---|---|
| Format: | Others |
| Language: | English |
| Published: |
Umeå universitet, Institutionen för datavetenskap
2019
|
| Subjects: | |
| Online Access: | http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-165182 |
| Summary: | This paper addresses the possibility of using version control and fixed merge pattern to ensure eventual consistency for collaborative work tools. Where the version control is upheld by a vector clock and used to detect conflicts. Which in turn are solved by rolling back to the last common version before using fixed merge pattern to create a new common version. In the fixed merge pattern a score system is used to lose as little work as possible. This is then tested against a leader node solution for the collaborative work tools. Which uplifts a FIFO consistency to sequential consistency by forcing all updates to go through the leader. The test used is a speed test to see if it is a viable solution or not to use when dealing with weak network connection. Since it would require less messages to be sent over the network compared to a leader node solution. |
|---|