3 ms·
Pinball is good for this use case. You can build a workflow include a few jobs, job1. generate a wav file, and put it somewhere say, s3://wav.file job2 (run a
by maoyesf 12y ago
Pinball is good for this use case. You can build a workflow include a few jobs,
job1. generate a wav file, and put it somewhere say, s3://wav.file
job2 (run after job1): pick the wav file from the location s3://wav.file
you need to know the contract between the parent and child jobs from the business logic. In this example, when you implement job 1 and job 2, you need to have protocol for them to produce store and consume the wav.file..
- jsmeaton 12y agoThanks for the reply. I'm wondering how you would share the location of the file between jobs though. Can job 1 output a file location that job 2 accepts as an input? I see there are plans to write up some documentation, but are there any timelines that you're aiming to have those written? Also, the README calls out mysql as being required. I assume that this, being a django project, will work with other backends too. Is there anything, to your knowledge, that would prevent a different backend being used (like postgres or oracle)?