QueryLeaf: SQL for Mongo

Would much rather have &quot;Mongo&quot; for SQL like this:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;microsoft&#x2F;documentdb">https:&#x2F;&#x2F;github.com&#x2F;microsoft&#x2F;documentdb</a><p>I am skeptical that SQL with Mongo backing it would be at all performant except in the most trivial cases. On the flip side, Postgres&#x27;s jsonb indexing makes the inverse very doable.

I can appreciate the technical aspect of a translation layer, but I struggle to understand the use case for a tool like this. If your data is inherently relational, then you should be using a relational store anyway. And if it isn&#x27;t, trying to hammer it on-demand into something that looks relational is going to eat you with performance implications. Unless I&#x27;m missing something.

It&#x27;s somewhat of a secret, but AWS&#x27;s JDBC driver for DocumentDB supports Mongo as well<p>Let&#x27;s you interact with Mongo as if it were a regular SQL JDBC database<p><a href="https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;amazon-documentdb-jdbc-driver">https:&#x2F;&#x2F;github.com&#x2F;aws&#x2F;amazon-documentdb-jdbc-driver</a>

Honestly, putting Mongo and SQL together always confuses me a bit. I&#x27;m way more comfy with Postgres and jsonb. Anyone else feel like scaling Postgres is still kinda a pain?