What does concurrency control mean in case of a self hosted state management? Referring to following:

• Concurrent state locking to prevent corrupting your infrastructure state in a team environment

For instance, you will need to manually configure secure access, encryption, and history, and devise your own concurrency control and recovery capabilities.

can anyone elaborate and also the implications of it?

we had asked this a while ago. The example i can use when A tries to create a resource (that may take a while to achieve a specific state) and in the midst of the creation, if B tries to delete the same (obviously the assumption is B knows the resource exists on some state at some point etc.). The cloud backend knows and locks that resource and no other operation can be done until it has reached the desired state.

thanks for clarifying1