Affects Version/s: None
Fix Version/s: 2.0
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.