4 ms·
The ability to run sandboxed workers from a PostgreSQL-based queue sounds useful all by itself, particularly for multi-tenant SaaS applications that need to do
by mwcampbell 4y ago
The ability to run sandboxed workers from a PostgreSQL-based queue sounds useful all by itself, particularly for multi-tenant SaaS applications that need to do compute-intensive tasks on untrusted inputs. The difference, of course, is that in this case, the worker implementation is part of the application, not a user-defined script. How tightly are the work queue and sandboxed worker runner coupled to the rest of the product?
- rubenfiszel 4y agoThey are tightly coupled at the moment but easy to extract out. I did not think there would be interest for that but I could carve it out as a separate dependency project for everyone to reuse! Here is the magic part to implement the queue in sql: https://github.com/windmill-labs/windmill/blob/main/backend/src/jobs.rs#L1384 https://github.com/windmill-labs/windmill/blob/main/backend/...
- ogarten 4y agoWe are thinking about creating something like this actually. We are still early-stage and haven't launched yet but we are looking for feedback and input to our idea. Would you mind talking to us about your problem?