2 ms·
I’m pretty sure this could fill a need for some people, especially given how different it is to operate in containerized environments compared to the old Linux
by xp84 1y ago
I’m pretty sure this could fill a need for some people, especially given how different it is to operate in containerized environments compared to the old Linux server cron situation.
It seems like there would be an advantage here that you should be advertising more prominently if you do it, and if you’re not doing it, maybe consider it:
Your application should be able to offer great visibility (and alerting, etc) to whether the tasks were acknowledged, and potentially whether they were successful (depending on whether they are so long-running that you don’t want to tie up a thread waiting for a super long HTTP request).
- rilesthefirst 1y agoHi xp84, thanks for the feedback! You’re totally right, visibility and monitoring are key, especially in containerized or distributed environments. In Orkera, you can already see past tasks, upcoming tasks, and their status, and you even have the ability to cancel tasks if needed. We also handle retries automatically. That said, making this more dashboard-friendly and alert-driven is definitely something we’re thinking about. Appreciate the insight, exactly the kind of feedback I’m looking for!