Redis for State Management of Time Tracking Time Entry
#13
Assignees
Labels
Comments
seyedali-dev
added
enhancement
seyedali-dev
added a commit
that referenced
this issue
May 20, 2024
#13) # Issue We encountered a `LazyInitializationException` when trying to access the `timeSegmentList` of a `TimeEntry` object that was retrieved from the cache. This happened because the `timeSegmentList` was lazily loaded by Hibernate, and we were trying to access it after the Hibernate Session had been closed. # Temporary Solution We resolved this issue by forcing the initialization of the `timeSegmentList` before caching the `TimeEntry` object. We did this by calling `size()` on the `timeSegmentList` in the `getTimeEntryById` method. This ensured that the list was fetched from the database and included in the cached `TimeEntry`. ```java timeEntry.getTimeSegmentList().size(); // This will initialize the timeSegmentList ``` > ## Note > This solution might have performance implications if the timeSegmentList is large, as it will always be fetched from the database even if it’s not needed. Therefore, this solution is not recommended for large data sets. We are currently exploring more efficient solutions.
seyedali-dev
added a commit
that referenced
this issue
May 20, 2024
Feature/redis state management - Close #13
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Persistence Across Restarts: If our application restarts or crashes, any in-memory data (like start times) would be lost. Redis can persist this data outside of our application’s process, allowing us to recover the state after a restart.
Scalability: As our application grows to handle more users, we might scale it across multiple servers. Redis provides a centralized place to store session data that all instances of our application can access, ensuring consistency across the system.
Performance: Redis is designed for high performance and can handle a large number of read/write operations very quickly, which is ideal for time-sensitive operations like time tracking.
The text was updated successfully, but these errors were encountered: