Feature Request: Adding Synchronization and Locks via AspectJ

[zdenek-jonas]

Feature Request: Adding Synchronization and Locks via AspectJ

Description:
Introduce an additional module in the store that provides a synchronization mechanism similar to the one used in Spring through Spring AOP. Spring Mutex Locking Eclipse Store docs
This module would leverage AspectJ technology, which is known to function outside of the Spring ecosystem, as outlined in resources such as this Baeldung article.

Key Features:

1. Optional Module: The module would be completely optional and isolated from the core functionality.
2. AspectJ Integration: It would utilize AspectJ for implementing synchronization mechanisms for shared mutable graphs.
3. Annotation-Based Control: Users willing to include AspectJ in their classpath and enable weaving would gain the ability to manage access to shared data elegantly using annotations.

This would offer a robust and streamlined solution for projects needing advanced synchronization without relying entirely on Spring.

    @Read
    public List<String> allJokes()
    {
    }
     

    @Write
    public Integer addNewJoke(String joke)
    {
    }

[fh-ms]

The new concurrency helpers can be used for that.

eclipse-serializer/serializer#156

[rpx99]

Is this feature meant to be a performance optimization for the synchronized keyword approach?

    public synchronized List<String> allJokes()
    {
    }
     
    public synchronized Integer addNewJoke(String joke)
    {
    }

[fh-ms]

It is meant to simplify the usage of ReentrantReadWriteLocks, which differentiate between read and write locks rather than just synchronizing.

[rpx99]

Understand. But how can I do something like optimistic locking or versioning to avoid conflicts between different users?

[fh-ms]

This is an approach to pessimistic locking. Versioning can be done with Layered Entities.