Oh, man. That's really unforunate. How will this affect dotmesh?
Dotmesh will remain open source and as the original author I'm happy to help maintain it. Are you using it or interested in using it?
Dotscience is shutting down
41–46 of 46 posts
Re: Dotscience is shutting down
#42It's really revealing that such amazing companies on paper...just don't make money at all and have to resort constantly to outside money to stay alive.
I think it's just took us too long to write the product as the scope was really big:
- CLI/UI.
- Main backend for storing projects, user accounts, managing pull requests, forks, runners, deployers, loadbalancers.
- Data backend (dotmesh).
- Auto provisioning of VMs with jupyterlabs running and data synced to GCP, AWS
- Runners that configure environment, install dependencies open up tunnels so users can access them and start working.
- Optimized machine imagine builds so the startup takes ~1min (some of the docker images like jupyter lab are very big)
- Model packaging into docker images.
- Model metrics capturing (a proxy that runs as a sidecar and intercepts requests) and then attaching relevant classes for your models.
- Kubernetes operator to deploy the actual models. User didn't have to worry about creating deployment manifests, services or ingresses (they wouldn't even care about docker images). They would just say which model to deploy and they would get a URL. Models could be deployed in a k8s cluster built from nodes with spot instances so would run pretty cheap :)
- Last component that I worked on was probably one of the most fun - an inference router that could allow canary deployments for models and also shadow deployments where traffic is sent to many models at once but responses are taken only from primary. We got a really nice UI for this as well where you could drag sliders around to configure % of traffic and so on. Unfortunately never managed to write docs for this.
- Terraform to wrap everything and deploy to GCP/AWS.
Our team was always quite small so we were stretched thin. In the end sales were going well as well, probably 6 more months and we would have broken even and then profitable :)
Re: Dotscience is shutting down
#43Oh, man. That's really unforunate. How will this affect dotmesh?
Dotmesh will remain open source and as the original author I'm happy to help maintain it. Are you using it or interested in using it?
Interested in using it. I've kept an eye on dotscience and dotmesh for quite some time. At work, we've only very recently ramped up Data Science and ML to a point where tools like these would be really helpful.
I loved all the demos of dotscience I've seen at conferences. I'm saddened that we'll never get to try it, but glad to see that dotmesh will live on!
Re: Dotscience is shutting down
#44Earlier quoted context omitted.
Hi, one of the engineers who created dotscience here. Customers didn't insist on open sourcing anything, we did have some open source components but I don't think they cared about that :) Regarding tracking usage - usually it was just many conversations with customers and having them on our Slack channel. Solutions engineering - mostly development team would be helping with writing anything specific that they need. O…
Thanks much for the response. So to sum up, what did customers care about the most from your point of view? (maybe top 3)
1. Deploying models easily (data scientist doesn't need to grok docker/kube)
2. Monitoring models including data and model drift/statistical monitoring (data scientists don't need to grok prom/grafana)
3. Only once these base concerns are met, model inventory, provenance, data versioning, reproducibility, collaboration with notebooks, ci integration etc.
Happy to talk more - drop me a note at luke@dotscience.com
Re: Dotscience is shutting down
#45It's really revealing that such amazing companies on paper...just don't make money at all and have to resort constantly to outside money to stay alive.
I think it's just took us too long to write the product as the scope was really big: - CLI/UI. - Main backend for storing projects, user accounts, managing pull requests, forks, runners, deployers, loadbalancers. - Data backend (dotmesh). - Auto provisioning of VMs with jupyterlabs running and data synced to GCP, AWS - Runners that configure environment, install dependencies open up tunnels so users can access them a…
Thanks for sharing! In hindsight, what would you skip? What were some high ROI features that were used frequently?
Re: Dotscience is shutting down
#46Oh, man. That's really unforunate. How will this affect dotmesh?
Dotmesh will remain open source and as the original author I'm happy to help maintain it. Are you using it or interested in using it?
I would love to help out keeping dothub alive. I had a few issues getting it to run but I think it is super cool! :))
I also filed a similar bug in github regarding open sourcing dothub.