# Relational databases, NoSQL, and downstream usage in AI models

**URL:** <https://accelerated-discovery.org/t/relational-databases-nosql-and-downstream-usage-in-ai-models/521>\
**Category:** Tools\
**Created:** [May 2, 2025, 8:32am UTC](https://accelerated-discovery.org/t/relational-databases-nosql-and-downstream-usage-in-ai-models/521 "2025-05-02T08:32:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aqui\_c](https://avatars.discourse-cdn.com/v4/letter/a/a4c791/32.png) [@aqui\_c](https://accelerated-discovery.org/u/aqui_c)\
**Post date:** [May 2, 2025, 8:32am UTC](https://accelerated-discovery.org/t/relational-databases-nosql-and-downstream-usage-in-ai-models/521/1 "2025-05-02T08:32:11Z")

</div>

I wonder what databases are you setting up for storing experiments, protocols, and results, to maximize the effectiveness when trying to run (perhaps speculating about the future) AI models on the generated data.

We are heavily reliant on relational databases (we mostly use PostgreSQL, and SQLite for simpler logging, etc.) and was wondering if anyone has explored NoSQL (like MongoDB) what’s the rationale, and what’s the outcome so far.

---

<div class="post-metadata">

**Author:** ![sgbaird](https://yyz1.discourse-cdn.com/flex003/user_avatar/accelerated-discovery.org/sgbaird/32/341_2.png) [@sgbaird](https://accelerated-discovery.org/u/sgbaird)\
**Post date:** [May 3, 2025, 11:01am UTC](https://accelerated-discovery.org/t/relational-databases-nosql-and-downstream-usage-in-ai-models/521/2 "2025-05-03T11:01:41Z")

</div>

Planning to come back to this, but some related discussion at:

> [@Database best practices for SDLs and database types (e.g., document, relational, knowledge graphs)](https://accelerated-discovery.org/t/database-best-practices-for-sdls-and-database-types-e-g-document-relational-knowledge-graphs/483):
>
> There are various database frameworks, some popular ones being document-based (e.g., MongoDB), relational (e.g., postgreSQL), and knowledge graph-based (e.g., neo4j). Generally a document-based one is easiest to get started with (especially given the parallels and user familiarity with Python dictionaries), but tends to adapt poorly as needs change and schema are updated. SQL and other relational databases have a long history, and while the entry barrier is generally higher, these seem to do r…