Jimmer Cache And Transaction AOP

[babyfish-ct]

Background

Within the scope of MUATION transaction, all queries should be executed directly without Jimmer Cache.

The applicaton does not use jimmer cache can ignore this discussion

• For in-transaction triggers, ignoring cache mens to avoid the cache problem caused by rollback.

• For binlog triggers, ignoring cache means to avoid the data sync problem cause by binlog delay.

Of course, the query operations automatically started by save command executes without cache, they are OK. However, what about query operations started by user?

Solution

Spring transaction have a readOnly flag, like @Transactional(readOnly = true), it allows users to mark whether a transaction is for query operations or mutation operation, this flag is not used by jimmer before.

• For readonly transaction, the injected sqlClient should be default sqlClient with cache.
• For non-readonly (mutation) transactions, the injected SqlClient should be direct client without cache.

Jimmer also supports it own transaction propagation mechanism such as sqlClient.transaction and @Tx (If jimmer-spring-starter is used, it wraps spring transaction, otherwise, provide a lightweight propagation mechanism like Spring), They should add the readOnly parameter too.

Affect

• Existing projects with jimmer cache need to review their @Transactional annotations because the behavior is adjusted.

• For Quarkus, can we implement the same approach? Input from someone familiar with Quarkus would be helpful.