4 ms·

Very cool. I have been thinking about analysis reproducibility lately and this is an interesting approach. I have two questions: 1) what is your business mod

by daveguy 11y ago

Very cool. I have been thinking about analysis reproducibility lately and this is an interesting approach. I have two questions: 1) what is your business model? I see a great open source project and some good information about why this is needed. However, I don't see any pricing for products or consulting. How are you making money? 2) It is good that you have shed the overhead of java and have the capability to interface with multiple languages. However, one complication I see that you have adapted is containerization. I understand the need and simplicity with respect to saving snapshots and reproducing results. However, interacting at the level of container manipulation is quite a bit of overhead for the average user. Is there a plan to add an simplifying interface layer on top of the container abstractions?

jdoliner 11y ago
Good questions both. We make money by offering support and services for Pachyderm. This includes a couple of things. Implementation services in which we help people setup a working Pachyderm cluster on their own infrastructure, help train their engineers on how to use the system and establish a plan for getting the company's data and analysis running on the new system. Support, where we help people with any issues that arise using the system. And consulting, where we get a lot more involved and help people actually build things on top of Pachyderm that their company needs. If you're interested in these services feel free to drop me a line at jdoliner@pachyderm.io We totally agree that containers aren't a suitable interface for everyone. We see containers as the ideal interface for developers. Over time we're expecting developers to build simpler interfaces on top of it. We'll also be building a lot of those ourselves. For example one feature we have on our near term roadmap is a SQL layer. We're going to implement that in terms of our container API which means that it should be very possible for a developer to implement a totally new access pattern just by throwing some code in a container.

by daveguy 11y ago

jdoliner 11y ago

Good questions both. We make money by offering support and services for Pachyderm. This includes a couple of things. Implementation services in which we help people setup a working Pachyderm cluster on their own infrastructure, help train their engineers on how to use the system and establish a plan for getting the company's data and analysis running on the new system. Support, where we help people with any issues that arise using the system. And consulting, where we get a lot more involved and help people actually build things on top of Pachyderm that their company needs. If you're interested in these services feel free to drop me a line at jdoliner@pachyderm.io We totally agree that containers aren't a suitable interface for everyone. We see containers as the ideal interface for developers. Over time we're expecting developers to build simpler interfaces on top of it. We'll also be building a lot of those ourselves. For example one feature we have on our near term roadmap is a SQL layer. We're going to implement that in terms of our container API which means that it should be very possible for a developer to implement a totally new access pattern just by throwing some code in a container.