[jira] [Updated] (CONFIGURATION-180) Cache DatabaseConfiguration values for higher performance

["Oliver Heger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CONFIGURATION-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Heger updated CONFIGURATION-180:
---------------------------------------
    Fix Version/s:     (was: 2.0)
                   2.x

> Cache DatabaseConfiguration values for higher performance
> ---------------------------------------------------------
>
>                 Key: CONFIGURATION-180
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-180
>             Project: Commons Configuration
>          Issue Type: Improvement
>            Reporter: Stephen Cooper
>            Assignee: Emmanuel Bourg
>            Priority: Minor
>             Fix For: 2.x
>
>         Attachments: ASF.LICENSE.NOT.GRANTED--Enhancement33553.checkstyle.patch, ASF.LICENSE.NOT.GRANTED--Enhancement33553.patch, ASF.LICENSE.NOT.GRANTED--dbpreload.txt
>
>
> The DatabaseConfiguration class queries each property as it gets the request for each property.  This is 
> nice for ensuring that you're always up to date, but it doesn't give very good performance in enterprise 
> applications, where the database may not be on the same subnet.
> What we need is the ability to hit the database once, get all the keys/values and then serve up 
> "getString" etc. from that cache.
> I'll be opening a separate enhancement to have a generic Reloading Strategy which could then be 
> applied to this caching DatabaseConfiguration approach.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)