Unless an xa source is being used, we would ideally use the default platform transaction manager. This would map updates over multiple sources to best effort single phase commit. This will likely be the majority of our usage.

The problem is that the platform transaction manager doesn't directly support a suspend/resume concept that is needed for our remote pg/jdbc processing logic that allows the processing thread to detach from the current work when blocked and do something else.

It would be worth investigating if this functionality could be added to spring boot or if there is is some other approach that was missed with the initial investigation.