[doc] add flowdapt integration to doc ecosystem page #45281
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following a discussion in the slack channel with @richardliaw, we are adding Flowdapt to the ecosystem page since it offers a robust workflow configuring/scheduling/triggering interface to Ray.
Some background on Flowdapt:
Over at Emergent Methods, we depend on Flowdapt for production workflow deployment for our product https://asknews.app. Meanwhile, we have a variety of other integrations such as Nowcast, which is designed to adaptively retrain/inference weather forecasting models on thousands of cities simultaneously. Some of our clients depend on Flowdapt for QAQC for high-throughput data analysis.
One cool feature of Flowdapt is that we designed it to accommodate a variety of backends, including Ray and Dask, as well as a local executor. Swapping between backends requires zero-code changes for the application - which allowed us to run a big apples-to-apples comparison of Ray vs Dask: https://docs.flowdapt.ai/examples/rayvsdask/. Spoiler alert: Ray wins.
Some open-source example plugins available that run on Flowdapt (and are best run with the Ray backend):
Weather forecasting:
https://github.com/emergentmethods/flowdapt-nowcast-plugin
Cryptocurrency price forecasting:
https://github.com/emergentmethods/flowdapt-cryptocast-plugin
Why are these changes needed?
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.