AsyncLock implementation isn't distributed
Closed this issue · 2 comments
miguelhasse commented
AsyncLock should be implemented as a distributed lock to support multi-instance storefront scenarios.
(this could be accomplished using Redis when it is enabled - http://redis.io/topics/distlock)
tatarincev commented
Thanks for suggestions, we have big expectations for the correct load balance distribution :) Use redis as redistributed cache and DLM may cause serious performance problems in production and we trying to avoid usage it. But if the reality does not leave us any choice we will have to take it on arms :)
tatarincev commented
The platform already has the support of hybrid cached data consistency policy.
https://virtocommerce.com/docs/vc2devguide/deployment/platform-scaleout