Best way to wrap Absinthe into Ecto transactions?

I’ve stomped into this post Using Ecto to run a long-running multi-process transaction and while may not be the best solution, it gives some ideas on how to approach the situation (unless the’re a more idiomatic ways).

basically certain “paths” maybe handled by the transaction manager, passing its pid using contexts or middleware.

what do you think?

back to the book now :slight_smile: