Hello, we have a project that works under umbraco v10.
We have implemented default authorization + authorization with UmbracoId, we also plan to add and manage users through Azure active directory.
We will have thousands of content editors that will be able to delete/edit and add the node document.
If you had such an experience, we want to know, were there any problems with the performance of the site/backoffice, or maybe there are some bugs or other problems associated with so many umbracos users.
If there are such problems, what methods can you recommend to fix this problem?
I can't comment on performance/bugs, but my initial thought would be this could lead to a whole heap of problems. With 'thousands' of content editors, the chances of more than one person editing the same content node at the same time would be pretty high.
lets say user A and user Z both open the same content node. user Z deletes the node, but user A edits it's name and saves, however the node will no longer exist because user Z deleted it.
Thousands of editors in umbraco backoffice
Hello, we have a project that works under umbraco v10.
We have implemented default authorization + authorization with UmbracoId, we also plan to add and manage users through Azure active directory.
We will have thousands of content editors that will be able to delete/edit and add the node document. If you had such an experience, we want to know, were there any problems with the performance of the site/backoffice, or maybe there are some bugs or other problems associated with so many umbracos users.
If there are such problems, what methods can you recommend to fix this problem?
I can't comment on performance/bugs, but my initial thought would be this could lead to a whole heap of problems. With 'thousands' of content editors, the chances of more than one person editing the same content node at the same time would be pretty high.
lets say user A and user Z both open the same content node. user Z deletes the node, but user A edits it's name and saves, however the node will no longer exist because user Z deleted it.
is working on a reply...