These are chat archives for dry-rb/chat
dry-transaction and wondering how one might facilitate long running tasks: eg.
step :preprocess_params enqueue :generate_report # long running, handled by exector/threadpool or sidekiq step :extract_and_parse_report_output step :persist_to_storage step :email_user_notification
I like the idea that the transaction encapsulates and clearly declares the end to end steps, but I can't think of a clean way to handle the async or long running task.
I could wrap the whole transaction call in a thread/threadpool....
what's the best practice around this?