[daveaiello]

I have used both SQL and NoSQL databases in the cloud. My sense of the situation at the moment is that some NoSQL databases have begun to focus on AI and LLM applications, apparently in order to provide scalable storage to these applications, which can be used for things like the persistence of state across many interactions.

However, there are always going to be legions of use cases for traditional database use, and the question continues to be, should everything that could need to scale massively use a NoSQL backend, or can some applications get by with something that looks like a traditional SQL architecture in 99+% of cases?

I think that many applications could be constructed with a NoSQL database as the backend for applications that are primarily reading content, while the applications that require the greatest access to CRUD functionality could interact with a SQL database using connection pooling to minimize resource utilization or latency at scale.

With this in mind, I could see applications where editing the backend is done in a SQL-based version of the database, while rendering content from the backend is done against a NoSQL version of the same database. There would probably be some momentary differences between the two, but the interface between the SQL and NoSQL version of the database could be a pipeline and therefore, could be optimized.