We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For longer running tasks, or which may require GPU or more resources, AWS Lambda functions may not be sufficient.
Is orkestra's current architecture capable of generating and dispatching AWS Batch job definitions? How hard would it be to implement such capability?
I suppose the Batch environment setup (job queue etc.) could be left to the user. orkestra could act more as generator for Step Functions definitions.
The text was updated successfully, but these errors were encountered:
Although I haven't yet tested, it should be possible to compose a batch task at the CDK layer like in this example.
I'll try it out and throw an example up soon.
Sorry, something went wrong.
I'd love an example, thanks. I have no experience with Python's CDK version and am still trying to understand how it all works.
Basically I'm looking for a workflow library integrated with AWS API Gateway/Lambda, Batch and Step Functions, so orkestra seems very promising.
Hope this helps @ogoid https://www.knowsuchagency.com/orkestra/examples/batch/ 😄
No branches or pull requests
For longer running tasks, or which may require GPU or more resources, AWS Lambda functions may not be sufficient.
Is orkestra's current architecture capable of generating and dispatching AWS Batch job definitions? How hard would it be to implement such capability?
I suppose the Batch environment setup (job queue etc.) could be left to the user. orkestra could act more as generator for Step Functions definitions.
The text was updated successfully, but these errors were encountered: