You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Matthew Reddington (Jira)" <ji...@apache.org> on 2020/11/17 21:57:00 UTC
[jira] [Created] (GEODE-8722) LRUMap isn't, and it's too large and
complex, needs refactoring.
Matthew Reddington created GEODE-8722:
-----------------------------------------
Summary: LRUMap isn't, and it's too large and complex, needs refactoring.
Key: GEODE-8722
URL: https://issues.apache.org/jira/browse/GEODE-8722
Project: Geode
Issue Type: Improvement
Components: native client
Reporter: Matthew Reddington
There exist trivial implementations of LRU caches which can be composed of a pair of standard maps, or a boost bi-map, which would be a more suitable replacement for our existing implementation. What we have makes no distinction between conceptual components - the map relies on the implementation details of its data type, which in turn relies on the implementation details of the map, and both share a dependency on the element expiration mechanism. Business logic is unnecessarily and tightly coupled to the implementation details of the map and has made the thing unmaintainable.
We need a more generic, loosely coupled, maintainable solution, where business logic is separate from the concept of a container.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)