Hello Folks,
In the series of articles, I will share some of the things which helped me to use the resources optimally.
Go through the below article to find out and have your suggestions if any in the comments.
Topic 2 : Avoid Conflicts during Deployment Pipeline
Generally, we follow certain technical best practices to enhance the platform performance but have you ever emphasized on internal working of business practices?
Scenario: Consider the case, where there are 15 developers of 2 different teams namely Team A and Team B
Admin 1 from Team A is working on ABC widget and simultaneously Admin 2 from Team B also working on the same widget.
After X days, Team B planning to move their changes to higher environment(Production)… so they moved it… After going live Team B realized that Team A changes are also deployed to production.
So, In order to avoid these conflicts in future we should put a lock on the resource where one developer is working.
Consider the above case but with concurrency avoidance and see how the scenario will play out.
- Logged in as “Admin” and updating the “ABC Widget”
- Simultaneously, “Admin 2” tries to work on the same widget and but system throws an error stating that the other developer is working on it.
- “Admin 2” tries again after few days, then the developer was able to access the widget as “Admin” completed with the development.
In this way we can avoid the conflicts during the deployment pipeline, the above is the jist of concurrency avoidance in widgets and the same can be applied for the other modules as well. Here I achieved the concurrency restriction with the help of versions.
Thanks,
Raghu ram.
