3 ms·
I'd love to learn more about what you're building--just reach out at peter.kraft@dbos.dev. One option is that you have DBOS workflows that schedule and submit
by KraftyOne 1y ago
I'd love to learn more about what you're building--just reach out at peter.kraft@dbos.dev.
One option is that you have DBOS workflows that schedule and submit jobs to an external worker app. Another option is that your workers use DBOS queues (https://docs.dbos.dev/python/tutorials/queue-tutorial https://docs.dbos.dev/python/tutorials/queue-tutorial). I'd have to better understand your use case to figure out what would be the best fit.
- blumomo 1y agoI’m also interested in what you think can become best practices where we can have (auto-scaling) worker instances that can pick up DBOS workflows and execute them. Do you think an app’s (e.g. FastAPI) backend should be the DBOS Client, submitting workflows to the DBOS instance? And then we can have multiple DBOS instances with each picking up jobs from a queue?
- KraftyOne 1y agoYeah, I think in that case you should have auto-scaling DBOS workers all pulling from a queue and a FastAPI backend using the DBOS client to submit jobs to the queue. Queue docs: https://docs.dbos.dev/python/tutorials/queue-tutorial https://docs.dbos.dev/python/tutorials/queue-tutorial Client docs: https://docs.dbos.dev/python/reference/client https://docs.dbos.dev/python/reference/client