#15 implement key expiration and cache eviction policy

[ezrasingh]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

Key Changes

This PR implements key expiration and a cache eviction policy, addressing issue #15. The key expiration is managed using a BTreeSet<(Instant, String)> to store expiration keys. To purge expired keys, the BTreeSet is split from the oldest keys up to Instant::now(), effectively targeting the subset of expired keys.

In the Geoprox server, a separate thread is spawned that runs in a sidecar state (Arc::clone of the app state). This thread executes an async loop that checks and removes expired keys every second.

Additional tests have been added to validate the purging process and the async loop runtime. Running cargo test is sufficient to verify the implementation.

Related Tickets & Documents

• Closes Implement Key Expiration and Cache Eviction Policy #15

QA Instructions, Screenshots, Recordings

To test the changes:

1. Run cargo test to validate the key expiration and cache eviction functionality.
2. Confirm that expired keys are purged correctly by examining the test results.

Added/updated tests?

• Yes
• No, and this is why: please replace this line with details on why tests have not been included
• I need help with writing tests