Fixes issue #16, but probably causes some performance degradation due to forcing the server thread to wait for IO.
Best would probably be to place a cache between the database and the Vault API, so that the value can be returned and changed without waiting on IO. A scheduled task could then flush dirty cache to the database in the background every second or so.
Fixes issue #16, but probably causes some performance degradation due to forcing the server thread to wait for IO.
Best would probably be to place a cache between the database and the Vault API, so that the value can be returned and changed without waiting on IO. A scheduled task could then flush dirty cache to the database in the background every second or so.