- Absolutely non-compromise precision - Bucket4j does not operate with floats or doubles, all calculation are performed in the integer arithmetic, this feature protects end users from calculation errors involved by rounding.
- Effective implementation in terms of concurrency:
- Bucket4j is good scalable for multi-threading case it by defaults uses lock-free implementation.
- In same time, library provides different concurrency strategies that can be chosen when default lock-free strategy is not desired.
- Effective API in terms of garbage collector footprint: Bucket4j API tries to use primitive types as much as it is possible in order to avoid boxing and other types of floating garbage.
- Pluggable listener API that allows to implement monitoring and logging.
- Rich diagnostic API that allows to investigate internal state.
- Rich configuration management - configuration of the bucket can be changed on fly
In additional to basic features described above, Bucket4j provides ability to implement rate-limiting in cluster of JVMs:
- Bucket4j out of the box supports any GRID solution which compatible with JCache API (JSR 107) specification.
- Bucket4j provides the framework that allows to quickly build integration with your own persistent technology like RDMS or a key-value storage.
- For clustered usage scenarios Bucket4j supports asynchronous API that extremely matters when going to distribute world, because asynchronous API allows avoiding blocking your application threads each time when you need to execute Network request.
In addition to local in-memory buckets, the Bucket4j supports clustered usage scenario on top of following back-ends:
| Back-end | Async supported | Optimized serialization | Thin-client support | Documentation link |
|---|---|---|---|---|
JCache API (JSR 107) |
No | No | No | bucket4j-jcache |
Hazelcast |
Yes | Yes | Planned | bucket4j-hazelcast |
Apache Ignite |
Yes | n/a | Yes | bucket4j-ignite |
Inifinispan |
Yes | Yes | No | bucket4j-infinispan |
Oracle Coherence |
Yes | Yes | No | bucket4j-coherence |
Bucket4j authors strongly recommends to use JVM based back-ends when possible, but for cases where it is not possible Bucket4j provides following integrations with non-JVM based storages:
In addition to local in-memory buckets, the Bucket4j supports clustered usage scenario on top of following back-ends:
| Back-end | Async supported | Documentation link |
|---|---|---|
Redis |
Yes | bucket4j-redis |
MySQL |
No | bucket4j-mysql |
PostgreSQL |
No | bucket4j-postgresql |
DynamoDb |
No | bucket4j-dynamodb |
Sometimes you are having deal with bucket per key scenarios but distributed synchronization is unnecessary, for example where request stickiness is provided by a load balancer, or other use-cases where stickiness can be achieved by the application itself, for example, Kafka consumer. For such scenarios Bucket4j provides support for following list of local caching libraries:
| Back-end | Documentation link |
|---|---|
Caffeine |
bucket4j-caffeine |
The Bucket4j is distributed through Maven Central:
<dependency>
<groupId>com.github.vladimir-bukhtoyarov</groupId>
<artifactId>bucket4j-core</artifactId>
<version>7.4.0</version>
</dependency>git clone https://github.com/vladimir-bukhtoyarov/bucket4j.git
cd bucket4j
mvn clean installFeel free to ask via:
- Bucket4j discussions for questions, feature proposals, sharing of experience.
- Bucket4j issue tracker to report a bug.
Copyright 2015-2021 Vladimir Bukhtoyarov Licensed under the Apache Software License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0.