Temporal is well suited for most asynchnous use cases, but if you can explain your usecase in detail, it will be useful.
In my usecase , i use temporal for manging customers signups, and orchestrating with pletheroa of internal systems when a user signup. (e.g create an account, set up user profile in identity system, set up some infrastructure things, provision a product on demand when the user signup for a specific product etc).
There is no official support for spring but is it one of the frequently demanded feature and high on priority list of temporal team.
My workplace is a big time spring boot shop,and with minimal custom coding , i was able to get temporal workfing with spring like a breeze (trust me its not very difficult, you will have to create a temporal factory thats about it).
As far as jpa/hibernate /transactions are concerned, you can use them with in the Activity. Activity can be your typical spring beans/ service/component, and has nothing to do wtih temporal. Temporals own data it manages through go-lang temporal in temporal server. The heavy lifting is done by temporal server component.
Your spring boot app will just include temporal sdk library to interact with temporal server thats it. And is free to use hibernate and other techonologies.
The Intercactio between temporal sdk and temporal server is on GRPC/protobuf.
If you are using netty/spring react depdency for starting the grpc part though…
Sof if you rest enpoints are also on GRPC/Protobut it will make your stack lean and you can take advantage of spring reactive .
if that s not a possible you can still run both the traditional spring web (http/json) stuff + grpc/protobuf for temporal in a single web app on differnt port too. (we do that in our setup and have faced no problems so far).
As far as Referece , refer temporal examples here
Here is an example of how few folks are integrating spring with temporal