Skip to Content (Press Enter)
2019-09-24 18-41-25
Jorge Martins
 
MVP
18Views
1Comments
[Synchronization Lock Extension] Behaviour in multiple front-end environments
Question
Forge
concurrency-locker-extension
Web icon
Synchronization Lock Extension (O11)
Forge asset by Matthew Stokes

Hi Matthew,

Nice to see new people coming up with interesting components, good work!

How would this library behave in an enterprise environment with multiple front-end servers?

Since the dictionary is in-memory, that would mean that different front-ends would not have the same locks in their dictionaries, right?

Thanks!

0
0
23 Apr 2020
Copy Link
2023-07-14 12-57-48
Matthew Stokes

Hi Jorge,

Thanks for the feedback. I believe you are correct and it is something I completely overlooked. Each front end server will no doubt have its own instance of the dictionary making this component mostly ineffective on a multiple front end server platform.

I will experiment with persisting the locks, I will lose some performance and I might just be pushing the problem further down (concurrently writing a lock in a table) but it will definitely solve the multiple front end server problem, and the limitation of the locks not being pervasive between e-spaces.

Any suggestions or ideas are welcome.

0
0
23 Apr 2020
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.