Inquir Compute launches today. What would you deploy first?
Inquir Compute launches on Product Hunt today at 12:01 AM Pacific.
The new release brings container apps and databases alongside functions and scheduled workflows. You can put a web app, its Postgres database and background work in one workspace, then follow releases and logs from the console or CLI.
You can start with:
A web app and its database.
An internal tool for your team.
A background worker or scheduled task.
There is a Free plan available on request, alongside Simple and Pro.
What would you try first, and what would you need to see before moving it from a local project to a running app?
31 views
Replies
Congrats on the launch! To your question: the first thing I'd move is a background worker, not the web app. Ours renders videos with ffmpeg and takes minutes per job, and that's exactly the kind of task that fits badly into plain functions. What I'd need to see before moving it: how a job that runs past the limit is handled, and whether I can read its logs while it's still running rather than after it dies.
For ffmpeg I would use a container worker. Applications have no idle timeout and you can stream logs while they run with inquir apps logs
A per-render deadline would need to be handled by the worker. Are you mainly worried about a stuck render or about work being interrupted during a deployment?
@al_kub mostly a stuck render. If a deployment interrupts the work I can just run the job again, nothing is lost but a minute. A render that hangs is worse, because the user is watching a progress screen and I only find out when they write to support. So a deadline inside the worker makes sense, and live logs would show me where it stopped. Thanks, that answers it.