Skip to content
Bluetape4k docs1.11

Ecosystem paths

Latest stable Based on Bluetape4k release 1.11.0

This module is an adapter between Spring Boot and the Hibernate cache provider.

Spring Boot properties / conditions
bluetape4k-spring-boot-hibernate-lettuce
↓ Hibernate properties
bluetape4k-hibernate-cache-lettuce
bluetape4k-cache-lettuce + Redis/Lettuce

The right source and tests depend on which layer owns the problem.

Read the bluetape4k-hibernate-cache-lettuce manual for region creation, keys, serialization, Caffeine L1, Redis L2, and invalidation. That module is also the entry point for configuring Hibernate properties without Spring.

For a general coroutine Near Cache and Lettuce client API, inspect bluetape4k-cache-lettuce and bluetape4k-lettuce without the Hibernate adapter. Do not add ORM to a cache with no entity regions or transaction lifecycle.

bluetape4k-spring-boot-hibernate-lettuce-demo connects a Product entity, Spring Data repository, CRUD controller, cache statistics endpoints, and a real application.yml.

A practical adoption path is:

  1. Read the demo settings and entity annotations.
  2. Validate application properties with this module’s context tests.
  3. Verify miss→put→hit with a real Redis and database.
  4. Expose Actuator and Micrometer dashboards only through the intended operations boundary.

Second-level cache reduces selected ORM read costs; it is not a reason by itself to choose ORM. Review entity lifecycle, lazy loading, and transactions in the bluetape4k-hibernate manual first.

Compare bluetape4k-jdbc for direct SQL control and bluetape4k-r2dbc for non-blocking drivers. For a Kotlin SQL DSL and repository ecosystem, continue to the bluetape4k-exposed repository. Hibernate second-level cache does not transfer unchanged to these choices.

External documentation follows its current release and can change. Use the release source and tests below for 1.11.0 behavior.