Hacker News Reader

Comment by chadly | Hacker News Reader

They are similar in that they are all job frameworks and you can run background jobs through them. Runly tries to be more prescriptive than Hangfire/Quartz in that jobs should process lists of items. We think this captures a lot of problems that developers deal with everyday. It also allows us to build goodies on top of jobs like multi-threading, retries, scaling, and UI status/progress. Check us out at https://www.runly.io

View on HN

Progress reporting is something my company's in-house offline processing system has been lacklustre at (we overloaded it with a ton of uses like chained processes, without considering the usability penalty when managing this without an appropriate UI).

Does Runly have some way to set up something like a dependency graph, such as

      /--B--\
  A---+     +---D
      \--C--/
  
  ---->time---->

such that it can show you "hey, part B failed and this is blocking part D"?

We provide rich components to use in your app to report status and progress of your jobs.

https://www.runly.io/ui/

Chained jobs/workflows is something that is on our roadmap.

Reply on news.ycombinator.com