[
https://issues.apache.org/jira/browse/FC-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18060128#comment-18060128
]
Shawn McKinney commented on FC-327:
-----------------------------------
Yes, I want to properly handle cache evictions. For most of the use cases it is
simple, as the cache holds one data structure (more below). The other use cases
are more problematic. What I tried to avoid is multiple round trips to the
server, especially during routine operations, that happen at runtime, during
routine security operations, like createSession.
What we need are local copies of 8 data structs. 4 are Simple Directed graphs
(one cache entry each), two are sets of strings (again one entry each) and two
are as described here, maps with multiple searchable keys, i.e. not one cache
entry.
Not interested in bringing in more infrastructure. The original appeal for
ehcache, was that for simple deployments, i.e. most, there was no need for
distribution and it was easy to manage. For complicated deployments, i.e.
multiple instances with enterprise SLA’s, distribution is possible. TBH, In the
15+ years that Fortress has been published, we don’t have a single documented
case where a service provider used, or asked for distribution. The typical way
to handle this (in practice) is routing administration requests through one
server, and having another on standby. Thus distribution not necessary for
consistent results during admin.
So, I’m no longer interested in distribution. A cache with a configurable TTL,
not distributed, and for 2 of the use cases, able to handle multiple keys is
good enough. Occasional misses are OK, assuming there is a refresh within a
reasonable amount of time, e.g. 10 minutes.
The idea, we added this new Role (something that happens seldom) and have to
wait 10 minutes for it to be used by users (in security operations). We can
live with that.
> Upgrade from ehcache v2
> -----------------------
>
> Key: FC-327
> URL: https://issues.apache.org/jira/browse/FC-327
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Shawn McKinney
> Priority: Major
> Fix For: 4.0.0
>
>
> Fortress core uses ehcache v2. It is getting long in tooth, has a number of
> CVE's, and needs to be replaced. Here we'll look at alternatives.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
