The current k8s and database transactions are separate, which will result in situations where a commit/processing failure of k8s will not trigger a rollback of a database transaction.
We need to design a unified transaction management or processing logic to ensure submarine-server to be able to handle exceptions and transaction rollbacks correctly.
For example, by using the @Transactional, or by putting the relevant operations codes/methods into one of our transaction services.
The current k8s and database transactions are separate, which will result in situations where a commit/processing failure of k8s will not trigger a rollback of a database transaction. We need to design a unified transaction management or processing logic to ensure submarine-server to be able to handle exceptions and transaction rollbacks correctly.
For example, by using the
@Transactional
, or by putting the relevant operations codes/methods into one of our transaction services.