Skip to content
New issue

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

How does ML Launchpad differ from Cortex #59

Open
schuderer opened this issue Jan 15, 2020 · 1 comment
Open

How does ML Launchpad differ from Cortex #59

schuderer opened this issue Jan 15, 2020 · 1 comment
Labels
faq (Candidates for) an FAQ in ML Launchpad

Comments

@schuderer
Copy link
Owner

schuderer commented Jan 15, 2020

Cortex is a new solution to make deploying machine learning solutions easier. What are the similarities and what are the differences to ML Launchpad?

@schuderer schuderer added needs discussion Several opinions should be heard and considered faq (Candidates for) an FAQ in ML Launchpad labels Jan 15, 2020
@schuderer
Copy link
Owner Author

schuderer commented Jan 15, 2020

Great to see that there are more and more solutions coming out in the last few months! People and companies who struggle with operationalizing ML stuff will have a lot of options to choose from! 😃

Some similarities I already see:

  • Python-based
  • Data Scientist fills in function body (for prediction), getting parameters as arguments, returning the prediction
  • Pickled models
  • Yaml-based config
  • Command line interface
  • Open source (Apache 2.0)
  • Does not prescribe the libraries to use

Some differences I see at first glance:

  • Designed for deployment to AWS (deployment prerequisites are considered out of scope for core ML Launchpad, which means you or your specialists have to solve the deployment pipeline (once), but for this you gain flexibility on where/how to deploy. We are open to suggestions on deployment tools to add to the ML Launchpad ecosystem, however. We try to keep ML Launchpad itself neat and clean, but having tooling as options is certainly possible.)
  • No train-test-predict(-retest-retrain)* life cycle support (ML Launchpad also includes model/api versioning, tracking of test metrics)
  • Functionality for tracking API calls (ML Launchpad currently only logs them)
  • Different APIs in one cortex config (each in a separate config in ML Launchpad)
  • No data abstraction builtin (vs. ML Launchpad's data sources, data sinks)
  • Batch API (in ML Launchpad you would typically use a data source as batch input. Extending ML Launchpad to support batch predictions with API-inputs would be possible, though. Please create an issue if this would be useful to you)
  • No R support
  • No file support as far as I can see
  • A company's product (Not sure how that affects whether what is open-sourced is actually the complete product or there some tools/parts that are still closed-source. I think the product is 100% open source and the monetization part is via support and consulting.)

I think it would actually be possible to combine Cortex with ML Launchpad, combining their advantages, and I plan to try it out when I find the time.

@schuderer schuderer reopened this Jan 15, 2020
@schuderer schuderer removed the needs discussion Several opinions should be heard and considered label Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
faq (Candidates for) an FAQ in ML Launchpad
Projects
None yet
Development

No branches or pull requests

1 participant