5 ms·

DuckDB raises 52M at 400M valuation

25 points by chirau 3y ago

datadrivenangel 3y ago
MotherDuck could be an incredible choice of data warehouse in terms of local development experience. A recurring painpoint I've seen at multiple data engineering organizations is the local development experience when using cloud data warehouses, so this is potentially very interesting.
- ryguyrg 3y ago
  spot on! we actually have a panel discussion on this at coalesce featuring matt housley and others. https://coalesce.getdbt.com/agenda/panel-discussion-fixing-the-data-eng-lifecycle https://coalesce.getdbt.com/agenda/panel-discussion-fixing-t... dbt folks actually brought this idea to us because it just makes so much sense -- no translating of sql between dev and prod. highlights from panel brainstorming from winnie @ dbt: Local development: should be fast, representative but not comprehensive of prod data, and independent of cloud services if I want that. The alternative has been that people typically use a schema in their production platform for development, CI workflows, etc. Costly and cloud-dependent. DuckDB and its role in facilitating the MDS-in-a-box pattern has been a game changer for local data development, which ramped up the ability to share data, modeling work, and analysis the way we share open source tooling, but syntax remained an issue for deployment.
jasmcole 3y ago
We settled on DuckDB as our in-browser DB at count.co - it's been great! Just waiting for extensions and compression in the WASM build now...
vgt 3y ago
Head of produck and co-founder at MotherDuck here. Happy to answer any questions! One minor correction on the title. While we're partners with DuckDB, and they're shareholders in MotherDuck, it is MotherDuck who raised the money, not DuckDB. On the plus side, we avoid the ethical dillemma of many OSS companies associated with being open-core - DuckDB is open, MotherDuck is closed (although contributing to open).
- datadrivenangel 3y ago
  Do you actually call yourself the produck team?
  - ryguyrg 3y ago
    ryan (co-founder) here. calling ourselves motherduck means we can either embrace the duck, or shy away from it. we've embraced it. tino's board slides do refer to it as the Produck team :-)
    - datadrivenangel 3y ago
      So is there is there any fowl play or competition with Marvin the Duck over at Prefect?
  - vgt 3y ago
    is there any other way to spell it?
    - ryguyrg 3y ago
      wait @tino, maybe we should call our support team the Pro Ducks team.
- datadrivenangel 3y ago
  More serious question: how are you positioning MotherDuck in terms of Cloud Data Warehouse versus Analytics tool?
  - vgt 3y ago
    I think we are much more than an analytics tool, but we don't yet have all the bells and whistles of the modern CDW. We think of ourselves as a new type of data warehouse - some things are different, but many things are the same. We actually just published a new produck page that talks about how we see ourselves at [0]. [0] https://motherduck.com/product/ https://motherduck.com/product/

25 points by chirau 3y ago

MotherDuck could be an incredible choice of data warehouse in terms of local development experience. A recurring painpoint I've seen at multiple data engineering organizations is the local development experience when using cloud data warehouses, so this is potentially very interesting.

ryguyrg 3y ago
spot on! we actually have a panel discussion on this at coalesce featuring matt housley and others. https://coalesce.getdbt.com/agenda/panel-discussion-fixing-the-data-eng-lifecycle https://coalesce.getdbt.com/agenda/panel-discussion-fixing-t... dbt folks actually brought this idea to us because it just makes so much sense -- no translating of sql between dev and prod. highlights from panel brainstorming from winnie @ dbt: Local development: should be fast, representative but not comprehensive of prod data, and independent of cloud services if I want that. The alternative has been that people typically use a schema in their production platform for development, CI workflows, etc. Costly and cloud-dependent. DuckDB and its role in facilitating the MDS-in-a-box pattern has been a game changer for local data development, which ramped up the ability to share data, modeling work, and analysis the way we share open source tooling, but syntax remained an issue for deployment.

jasmcole 3y ago

We settled on DuckDB as our in-browser DB at count.co - it's been great! Just waiting for extensions and compression in the WASM build now...

vgt 3y ago

Head of produck and co-founder at MotherDuck here. Happy to answer any questions! One minor correction on the title. While we're partners with DuckDB, and they're shareholders in MotherDuck, it is MotherDuck who raised the money, not DuckDB. On the plus side, we avoid the ethical dillemma of many OSS companies associated with being open-core - DuckDB is open, MotherDuck is closed (although contributing to open).

datadrivenangel 3y ago
Do you actually call yourself the produck team?
- ryguyrg 3y ago
  ryan (co-founder) here. calling ourselves motherduck means we can either embrace the duck, or shy away from it. we've embraced it. tino's board slides do refer to it as the Produck team :-)
  - datadrivenangel 3y ago
    So is there is there any fowl play or competition with Marvin the Duck over at Prefect?
- vgt 3y ago
  is there any other way to spell it?
  - ryguyrg 3y ago
    wait @tino, maybe we should call our support team the Pro Ducks team.
datadrivenangel 3y ago
More serious question: how are you positioning MotherDuck in terms of Cloud Data Warehouse versus Analytics tool?
- vgt 3y ago
  I think we are much more than an analytics tool, but we don't yet have all the bells and whistles of the modern CDW. We think of ourselves as a new type of data warehouse - some things are different, but many things are the same. We actually just published a new produck page that talks about how we see ourselves at [0]. [0] https://motherduck.com/product/ https://motherduck.com/product/