Creating custom JDBC wrapper for serialization/deserialization #505
-
We have a database/data source that is not supported by bucket4j.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hello @pranjalc92
I suppose that it will be unpleasure excersize. The main problem will be correctness in concurrent environment.
At least on-the-fly configuration replacement and implicit configuration replacement. And you will not be able to reuse AbstractDistributedBucketTest to check whether you solution is correct or not. So I highly reccomend to extend one of base classes(choose particular depending from concurrency features that your database provides) instead of writing all code from scratch:
Extending one of base class will allow to resuse the TCK and reuse ideas from already implemented integrations.
Refill should works fine, in way way as you proposed. |
Beta Was this translation helpful? Give feedback.
Hello @pranjalc92
I suppose that it will be unpleasure excersize. The main problem will be correctness in concurrent environment.
At least on-the-fly configuration replacement and implicit configuration replacement. And you will not be able to reuse AbstractDistributedBucketTest to check whether you solution is correct or not. So I highly reccomend to extend one of base classes(choose particular depending from concurrency features that your database provides) instead of writing all code from scratch: