问HN：你们现在还在使用Redis和工作进程仅仅为了后台任务吗？
嗨，HN，
我正在开发一些小型SaaS项目，但总是遇到同样的问题：后台任务需要大量的基础设施。即使是简单的延迟任务或定时作业，我也不得不运行Redis、队列工作者、定时任务、重试、监控等。对于较大的系统来说，这样做是有意义的，但对于小型应用来说，这似乎有些过于复杂。
我在考虑构建一个小型服务，允许你通过API发送任务，并在执行时间到达时获得HTTP回调，而无需自己运行队列或工作者。基本上：不需要Redis，不需要工作者，不需要定时任务，不需要队列服务器。
像这样的服务真的有用吗，还是我在试图解决一个并不存在的问题？
查看原文
Hi HN,<p>I'm working on small SaaS projects and keep running into the same issue: background jobs require a lot of infrastructure.
Even for simple things like delayed tasks or scheduled jobs I end up running Redis, queue workers, cron, retries, monitoring, etc.
For bigger systems this makes sense, but for small apps it feels like too much.<p>I'm thinking about building a small service that would let you send a job via API and get an HTTP callback when it's time to run, without running your own queue or workers.
Basically: no Redis, no workers, no cron, no queue server<p>Would something like this actually be useful, or am I trying to solve a problem that isn't really there?