3 ms·
Congrats on the launch! It’s great to see validation of the usefulness of notebooks in data workflows even when moving beyond the proof of concept/exploration s
by ricklamers 5y ago
Congrats on the launch! It’s great to see validation of the usefulness of notebooks in data workflows even when moving beyond the proof of concept/exploration stage into production type workloads and deployments. Once deployed, iteration is often still necessary or desirable and that’s where having notebooks available for continued iteration is a big advantage.
For those who’d like to compare and contrast different solutions that support the use of notebooks in the (batch) deployment context you can also check out Orchest (https://github.com/orchest/orchest https://github.com/orchest/orchest). I’d say a meaningful point of difference between Ploomber and Orchest is that we are more container oriented as we’ve found that gives robust units to deploy in production with isolated and well defined dependencies. In addition we have a more GUI first approach which might be more familiar to those who come from RStudio, JupyterLab, Spyder, MATLAB, etc.
Disclaimer: I’m one of the Orchest creators.
- sails 5y agoNothing in the orchest docs looked to me like a deployment setup, whereas I came across a few ploomber cloud deployment related docs eg: https://soopervisor.readthedocs.io/en/latest/tutorials/aws-batch.html https://soopervisor.readthedocs.io/en/latest/tutorials/aws-b... Please point me in the right direction?
- ricklamers 5y agoGlad you asked. Simply deploy the Orchest OSS to a VM of choice (https://docs.orchest.io/en/latest/getting_started/installation.html https://docs.orchest.io/en/latest/getting_started/installati...) or use https://cloud.orchest.io https://cloud.orchest.io and then create scheduled Jobs. https://docs.orchest.io/en/latest/fundamentals/jobs.html https://docs.orchest.io/en/latest/fundamentals/jobs.html If you’re looking for something more than that I’d be happy to open up a conversation about your use case at rick@orchest.io