Testing, operations, and ecosystem paths
Latest stable Based on Bluetape4k release 1.11.0
Test the client that owns the behavior
Section titled “Test the client that owns the behavior”infra/redis has no production or test source. A successful :bluetape4k-redis:test task therefore does not validate connections, coroutines, Codecs, or distributed objects. Run the selected submodule tests and application integration tests.
./gradlew :bluetape4k-lettuce:test --no-build-cache --no-configuration-cache./gradlew :bluetape4k-redisson:test --no-build-cache --no-configuration-cacheBoth suites start Redis with Testcontainers. Do not run them in parallel with other database or broker Testcontainers suites. Documentation-only changes use release-source link, locale-structure, and Markdown checks instead of heavy tests.
Small executable examples
Section titled “Small executable examples”| Contract | Representative test |
|---|---|
| Lettuce client, cached connection, shutdown | LettuceClientsTest.kt |
RedisFuture results and failure propagation | RedisFutureSupportTest.kt |
| Redisson configuration, batch, transaction | RedissonClientSupportTest.kt |
| Stream groups and consumer helpers | RStreamSupportTest.kt |
Read each example under the module that owns the API rather than presenting them as umbrella tests.
Operational baseline
Section titled “Operational baseline”When both clients are active, keep metrics separated by client:
- connections, pool use, and reconnects;
- command latency, timeouts, and retries;
- pending asynchronous work and coroutine cancellation;
- Codec failures and schema versions per key prefix;
- Redisson Stream pending entries and Near Cache stale incidents;
- shutdown duration and undrained queues.
After replacing the umbrella with one dependency, verify that threads, connections, and metrics for the removed client disappear.
Ecosystem learning path
Section titled “Ecosystem learning path”- Read the complete Lettuce manual or Redisson manual for the chosen client.
- Use Cache Core to learn cache-aside and failure contracts before choosing a provider.
- Continue to Lettuce Cache or Redisson Cache.
- For Hibernate second-level caching, inspect regions and transactions in Hibernate Cache Lettuce.
- Practice cache and repository boundaries in Exposed Workshop and bluetape4k-workshop.
The umbrella is a build convenience layer in this path, not another functional layer. Organize learning and operations around the selected client and provider.