21–30 of 73 posts
This is great work! Could you please comment on the choice of your license. Lost Postgres extension that achieve wide adoption use Postgres, MIT or Apache license.
Neat that you plan to support both Delta Lake and Apache Iceberg I'm curious about HN's position between these two formats? I'm having a hard time deciphering which might be the industry winner (or perhaps they both have a place, no "winner" necessary)
There isn't a winner and there likely won't be one (at least not for a long time). Tabular will likely be acquired by Snowflake and the two industry behemoths now back their own formats, and each will treat their own as a first class citizen.
https://en.wikipedia.org/wiki/P._G._Wodehouse
Very clever naming!
This is great work! Could you please comment on the choice of your license. Lost Postgres extension that achieve wide adoption use Postgres, MIT or Apache license.
All ParadeDB extensions are released under AGPL-3.0. We've found that it strikes the right balance between being open-source and enabling the community to adopt for free, while also protecting us from hyperscalers and enabling us to build a sustainable business. Perhaps the topic of a blog post someday :)
The name seems to be an allusion to the author P.G. Wodehouse, creator of the character Jeeves. https://en.wikipedia.org/wiki/P._G._Wodehouse Very clever naming!
https://www.databricks.com/product/data-lakehouse
edit: ah, but in a different comment someone noted that it's not actually a lakehouse, so who knows!? :)
The name seems to be an allusion to the author P.G. Wodehouse, creator of the character Jeeves. https://en.wikipedia.org/wiki/P._G._Wodehouse Very clever naming!
Sorry, what do you base that on? To me it just seems like a straightforward inspiration from the "data lake" -> "lakehouse" terminology that Databricks started (?) using. https://www.databricks.com/product/data-lakehouse edit: ah, but in a different comment someone noted that it's not actually a lakehouse, so who knows!? :)
My best guess is that Databricks and Pg_lakehouse both independently coined "lakehouse" from "data lake", and that for the latter team, it was partly a pun on Wodehouse. But the creators are welcome to chime in and confirm/deny!
(Or to say, like, "Sure...uh, we totally meant that...yes we are very literary.")
Earlier quoted context omitted.
All ParadeDB extensions are released under AGPL-3.0. We've found that it strikes the right balance between being open-source and enabling the community to adopt for free, while also protecting us from hyperscalers and enabling us to build a sustainable business. Perhaps the topic of a blog post someday :)
It looks like hyper scalers can still host it as long as they are publishing changes to the source code ? Am I reading the license right ?
Earlier quoted context omitted.
It looks like hyper scalers can still host it as long as they are publishing changes to the source code ? Am I reading the license right ?
For aws to make it available on rds Aurora, would it be safe to assume there would have to be some changes to the extension source to make it compatible with the Aurora engine? If we assume aws doesn’t want todo that, then their licensing provides some protection there.
Earlier quoted context omitted.
Sorry, what do you base that on? To me it just seems like a straightforward inspiration from the "data lake" -> "lakehouse" terminology that Databricks started (?) using. https://www.databricks.com/product/data-lakehouse edit: ah, but in a different comment someone noted that it's not actually a lakehouse, so who knows!? :)
Based on pure speculation. I may be reaching. My best guess is that Databricks and Pg_lakehouse both independently coined "lakehouse" from "data lake", and that for the latter team, it was partly a pun on Wodehouse. But the creators are welcome to chime in and confirm/deny! (Or to say, like, "Sure...uh, we totally meant that...yes we are very literary.")