Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lakebase architecture delivers faster Postgres writes

databricks.com

Post reply on HN
Print view View original

11–20 of 39 posts

Re: Lakebase architecture delivers faster Postgres writes

#13

Post by gavinray »

So, the general architecture described here is solid, and I support it, but I take issue with the "Lakebase" naming thing.

Disaggregated storage and disaggregated compute have been an open trend in DBMS development for the last half-decade. This is an obvious move with modern computing paradigms, and the academic literature has a standard name for it.

This feels like "JAMStack" from Netlify happening all over again.

I tweeted about this in 2022, as a general trend, and also from the RocksDB meetup emphasizing disaggregated storage:

- https://x.com/GavinRayDev/status/1607769112234823680

- https://x.com/GavinRayDev/status/1600666127025156096

Re: Lakebase architecture delivers faster Postgres writes

#15

Post by jeremyjh »

gavinray wrote: post #13

So, the general architecture described here is solid, and I support it, but I take issue with the "Lakebase" naming thing. Disaggregated storage and disaggregated compute have been an open trend in DBMS development for the last half-decade. This is an obvious move with modern computing paradigms, and the academic literature has a standard name for it. This feels like "JAMStack" from Netlify happening all over again.…

I don't think it should be surprising that vendors are not going to lead with "disaggregated storage". I don't see that taking off either. This isn't a paper in a journal. Aurora doesn't call it that either. But yes, it is not a new idea.

Re: Lakebase architecture delivers faster Postgres writes

#16

Post by nikita »

gavinray wrote: post #13

So, the general architecture described here is solid, and I support it, but I take issue with the "Lakebase" naming thing. Disaggregated storage and disaggregated compute have been an open trend in DBMS development for the last half-decade. This is an obvious move with modern computing paradigms, and the academic literature has a standard name for it. This feels like "JAMStack" from Netlify happening all over again.…

Lakebase is referring to the fact that in addition to disaggregated storage s3 is authoritative storage for older data.

Since data is on s3 (or lake) you can perform direct to s3 type operations like data loading, reading this data by engines that are not Postgres and more

Re: Lakebase architecture delivers faster Postgres writes

#17

Post by gavinray »

jeremyjh wrote: post #15
gavinray wrote: post #13

So, the general architecture described here is solid, and I support it, but I take issue with the "Lakebase" naming thing. Disaggregated storage and disaggregated compute have been an open trend in DBMS development for the last half-decade. This is an obvious move with modern computing paradigms, and the academic literature has a standard name for it. This feels like "JAMStack" from Netlify happening all over again.…

I don't think it should be surprising that vendors are not going to lead with "disaggregated storage". I don't see that taking off either. This isn't a paper in a journal. Aurora doesn't call it that either. But yes, it is not a new idea.

Avoiding industry-standard names and trying to introduce your own convention comes off as hubristic and grift-ey to me.

"Basic literacy" -> "Prompt Engineering"

"P2P networking" -> "Web3"

"Service-Oriented Architecture" -> "Microservices"

Maybe I'm old-man-yelling-at-cloud.

Re: Lakebase architecture delivers faster Postgres writes

#18

Post by gavinray »

nikita wrote: post #16
gavinray wrote: post #13

So, the general architecture described here is solid, and I support it, but I take issue with the "Lakebase" naming thing. Disaggregated storage and disaggregated compute have been an open trend in DBMS development for the last half-decade. This is an obvious move with modern computing paradigms, and the academic literature has a standard name for it. This feels like "JAMStack" from Netlify happening all over again.…

Lakebase is referring to the fact that in addition to disaggregated storage s3 is authoritative storage for older data. Since data is on s3 (or lake) you can perform direct to s3 type operations like data loading, reading this data by engines that are not Postgres and more

  > in addition to disaggregated storage s3 is authoritative storage for older data
Suppose a person retrives cold data from another Object Storage protocol rather than S3. This is no longer a "Lakebase", so we have to come up with a different name to avoid confusion.

But if you say "Disaggregated Storage on S3" then you have the flexibility to change that to "Disaggregated Storage on FOOBAR" to avoid confusion.

Re: Lakebase architecture delivers faster Postgres writes

#20

Post by jeremyjh »

gavinray wrote: post #17
jeremyjh wrote: post #15

Earlier quoted context omitted.

I don't think it should be surprising that vendors are not going to lead with "disaggregated storage". I don't see that taking off either. This isn't a paper in a journal. Aurora doesn't call it that either. But yes, it is not a new idea.

Avoiding industry-standard names and trying to introduce your own convention comes off as hubristic and grift-ey to me. "Basic literacy" -> "Prompt Engineering" "P2P networking" -> "Web3" "Service-Oriented Architecture" -> "Microservices" Maybe I'm old-man-yelling-at-cloud.

Its more like old-man-yelling-at-billboard. Its just marketing. Its like complaining about the font they chose.
Post reply on HN