4 ms·

How does this differ with Postgres AI's thin cloning and database branching? https://github.com/postgres-ai/database-lab-engine https://github.com/postgres-ai/

by wdb 3y ago

How does this differ with Postgres AI's thin cloning and database branching? https://github.com/postgres-ai/database-lab-engine https://github.com/postgres-ai/database-lab-engine

nalexpear 3y ago
It's very similar! Postgres.ai is built on ZFS and is a separate application that manages the file system and its branches/"thin clones". pg_branch is an extension that hooks directly into Postgres's own commands (specifically, CREATE DATABASE) to trigger branching.
vb-8448 3y ago
Postgres AI seems to be a "managed solution" while this is an extension you could use on your self-hosted instance. But, under the hood, they are very similar.
- samokhvalov 3y ago
  Underlying DBLab Engine is FOSS (Apache 2.0), with API, CLI and UI https://github.com/postgres-ai/database-lab-engine https://github.com/postgres-ai/database-lab-engine
  - klysm 3y ago
    Yea but there’s incentive to obscure it given the managed solution. I view it as high risk
    - samokhvalov 3y ago
      Well, understandable. This is true for any open-source product that is under control by a single company and the majority of contributions comes from this company. Yes, we aim to have revenue (as any company) from our paid offering. But not only we're going to keep DBLab Engine open and free, we recently changed the license from AGPLv3 to Apache 2.0, and currently consider making additional pieces open.
      - klysm 3y ago
        Very glad to see the change to Apache license, and super happy the code is even source available. I was more referring to the perverse incentives that every company built around open source faces with regards to documentation. It may be less so the case here, but there probably is some incentive to make the docs subpar, or not a strong incentive to make them fantastic - it’s a difficult thing to balance. Side note: I’ve been loving the Postgres.FM episodes, thanks so much for doing them!

by wdb 3y ago

How does this differ with Postgres AI's thin cloning and database branching? https://github.com/postgres-ai/database-lab-engine https://github.com/postgres-ai/database-lab-engine

nalexpear 3y ago

It's very similar! Postgres.ai is built on ZFS and is a separate application that manages the file system and its branches/"thin clones". pg_branch is an extension that hooks directly into Postgres's own commands (specifically, CREATE DATABASE) to trigger branching.

vb-8448 3y ago

Postgres AI seems to be a "managed solution" while this is an extension you could use on your self-hosted instance. But, under the hood, they are very similar.

samokhvalov 3y ago
Underlying DBLab Engine is FOSS (Apache 2.0), with API, CLI and UI https://github.com/postgres-ai/database-lab-engine https://github.com/postgres-ai/database-lab-engine
- klysm 3y ago
  Yea but there’s incentive to obscure it given the managed solution. I view it as high risk
  - samokhvalov 3y ago
    Well, understandable. This is true for any open-source product that is under control by a single company and the majority of contributions comes from this company. Yes, we aim to have revenue (as any company) from our paid offering. But not only we're going to keep DBLab Engine open and free, we recently changed the license from AGPLv3 to Apache 2.0, and currently consider making additional pieces open.
    - klysm 3y ago
      Very glad to see the change to Apache license, and super happy the code is even source available. I was more referring to the perverse incentives that every company built around open source faces with regards to documentation. It may be less so the case here, but there probably is some incentive to make the docs subpar, or not a strong incentive to make them fantastic - it’s a difficult thing to balance. Side note: I’ve been loving the Postgres.FM episodes, thanks so much for doing them!