It is no surprise that streaming technologies such as meteor have taken the spotlight over the last year. They present a compelling real-time way of keeping the client in sync with the server. One interesting result of thinking in real-time is that things like conflicts become top of mind: what is supposed to happen when two separate users modify the same data at the same time?
When dealing with traditional websites and basic REST API's, however, less thought is given to these concurrency scenarios. Real-time aside, in an age where client-heavy applications are becoming commonplace, this behavior can be problematic. In this post, I explore this inadequacy and also explore a possible solution.