3 ms·

Hi Windmill devs -- why build this on relational Postgres at all? I've been toying with the idea of forking airflow and trying to swap out the backend for somet

Hi Windmill devs -- why build this on relational Postgres at all? I've been toying with the idea of forking airflow and trying to swap out the backend for something document based either on Mongo or something else. The reasons being db migrations are a pain in the relational strongly typed schema world vs the more forgiving paradigm of documents.

cyanydeez 3y ago
what'd be wrong just storing your documents in postgres JsoN Or XML fields
- DonnyV 3y ago
  Because Postgres is a relational database.
  - cyanydeez 3y ago
    that wasn't the concern being presented. The concern is "I want to store mostly unknown structured data, so why dont I use a DB already stupd to do that"
- gigatexal 3y ago
  That could work too I guess.
rubenfiszel 3y ago
because 95% of the tables you need for this are relational (queue, completed_job, users, etc, etc) and for the few things that are unstructured, you can represent them well in PG with JSONB (which is what we do for inputs and outputs).