Congrats Jeff, Ryan, Antony, Dan, Sheila!
2,349 karma · joined September 12, 2014
Shameless plug - if you love DuckDB but don't want to manage it yourself, or if you need a supported 3rd party ecosystem, sharing/IAM, a fully-fledged beautiful web UI - all the things beyond DuckDB that are important to adapt DuckDB as a solution - I encourage you to look at MotherDuck. You can sign up in seconds (about 17 seconds, I timed it), you get a 30 day Free Trial without having to put in a credit card. We also offer a perpetual Free Tier and a Startup Program for qualifying startups.
(co-founder at MotherDuck)
Feel free to reach out to tino@motherduck.com.
(Co-founder)
- Managed storage with zero-copy clone (and upcoming time travel)
- Secure Sharing
- Hybrid Mode that allows folks to combine client (WASM, UI, CLI, etc) with cloud data
- Approved and supported ecosystem of third party vendors
- Since we're running DuckDB in production, we're working very closely with the DuckDB team to improve both our service and open source DDB in terms of reliability, semantics, and capabilities
(co-founder at MotherDuck)
We at MotherDuck took an incremental approach. We launched something more akin to lane-assist. We're calling it FixIt - an in-flow visual aid to help you identify and fix errors in your SQL [0].
I think there's gobs of opportunities to improve the analytics experiences without resorting to "L5 self-driving" (e.g. full text-to-results)
[0] https://motherduck.com/blog/introducing-fixit-ai-sql-error-f...
What's really exciting is what you can do with DuckDB, MotherDuck, and WASM. A powerful in-browser storage and execution engine tethered to a central serverless data warehouse using hybrid mode [1] opens the doors for unprecedented experiences. Imagine the possibilities if you have metadata, data, query logic, or even LLMs in the client 0ms away from the user and on user's own hardware.
So we're doing this in our UI of course, but we also released a WASM SDK so that developers can take advantage of this new architecture in their own apps! [2]
[0]https://motherduck.com/blog/introducing-fixit-ai-sql-error-f...
[1]https://motherduck.com/docs/architecture-and-capabilities
(head of produck at MotherDuck)
Global economy relies on this stability, and US benefits the most from the stability of the global economy.
We also didn't "spend 75 billion dollars". Very little actual cash went to Ukraine from the US. We gave them old stockpiles, which we were going to decommission anyway, and paid maintenance for. We also paid US companies to increase production (of ammunition for example), and given that the Russia conflict is increasing demands for ammunition, increasing supply is not a bad thing.
This is such a lazy talking point permeating conservative spheres. And it quite likely coming straight from Russia psy-ops.
(co-founder and head of produck, feel free to reach out)
"The team at DuckDB Labs has been hard at work improving the performance of the out-of-core hash aggregates and joins."
Aside from that, since April DuckDB has vastly improved performance of a number of queries, including aggregates, joins, window functions. [0]
[0] https://duckdb.org/2023/09/26/announcing-duckdb-090.html#cor...
Yes, we are indeed a good use case for this. For one, we built a fully-fledged managed storage system on top of DuckDB, with better performance and caching and the like. Two, we're going to be pretty good at reading from S3 because we've optimized that path. Three, our storage has sharing/IAM and is about to have things like zero-copy clone and time travel.
Happy to answer any Qs.
(Head of Produck at MotherDuck and a huge fan of DuckDB)
One of the reasons we exist is because DuckDB is meant to be a single-player database. MotherDuck is doing tons of heavy-lifting to turn it into a true multi-player data warehouse, so things like IAM/sharing, persistence, time travel, administration, the ecosystem and so forth.
What's magical about MotherDuck is that virtually any DuckDB instance in the wild can connect to MotherDuck by simply running '.open motherduck:' [1], and suddenly you get all these aforementioned benefits.
(head of produck at MotherDuck)
[1] https://motherduck.com/docs/getting-started/connect-query-fr...
And do you think it's hypocritical for a "proponent of free speech" to threaten to sue entities that quantify and observe such a rise? [1]
[0] https://www.theguardian.com/technology/2023/sep/26/eu-warns-...
[1] https://www.cnn.com/2023/07/31/tech/twitter-lawsuit-hate-spe...
(Head of Produck and Co-founder at MotherDuck)
Storage is naturally distributed due to underlying IaaS.
Rather, that seems to be an implementation detail. What use cases are relevant is the key. Are we chasing big Apple-sized workloads? No. [1]
That said, scaling-up on EC2, especially with our one-instance-per-user architecture, fits vast majority of workloads we've seen in our past lives building Exabyte-scale systems.
[0] https://motherduck.com/blog/the-simple-joys-of-scaling-up/ [1] https://motherduck.com/blog/big-data-is-dead/
While we're running vanilla duckdb, our extension does sopen heart surgery on some of the components, to make it suitable for a multi tenant serverless cloud service.
(Co-founder and head of produck at MotherDuck)
We actually just published a new produck page that talks about how we see ourselves at [0].
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).