> every profile synchronization service I've ever encountered has had severe failure scenarios. I guess it makes sense when you think of it as a CAP theorem problem
I don't think CAP theorem is particularly relevant in this scenario. Sounds more like they were doing an overly basic "just overwrite with the current state" instead of sending individual commands, e.g. "create this bookmark".
The reason is likely a procurement problem. Anything that's "enterprise" and calls things "endpoints" is off to a bad start in my book.
I don't think CAP theorem is particularly relevant in this scenario. Sounds more like they were doing an overly basic "just overwrite with the current state" instead of sending individual commands, e.g. "create this bookmark".
The reason is likely a procurement problem. Anything that's "enterprise" and calls things "endpoints" is off to a bad start in my book.