MongoDB VS PostgreSQL

The MongoDB JavaScript driver uses and requires node.js, which is what 99.9% of server-side JavaScript implementations use.

Mongo Drivers

If you look at how major backend projects structure their code, it's almost always object-oriented TypeScript.

I submit for the record:

- Apollo Client: https://github.com/apollographql/apollo-client/blob/main/src...

- Storybook: https://github.com/storybookjs/storybook/blob/next/lib/chann...

- Nest: https://github.com/nestjs/nest/blob/master/packages/core/nes...

- MongoDB Driver: https://github.com/mongodb/node-mongodb-native/blob/main/src...

- Prisma: https://github.com/prisma/prisma/blob/main/packages/engine-c...

The MongoDB Node.js Driver, to save data to MongoDB;

The error probably is a MongoServerError, not MongoError, see https://github.com/mongodb/node-mongodb-native/blob/HEAD/etc/notes/errors.md

The most basic way to interact with MongoDB is using the Official MongoDB Node.js Driver, in this guide we will use Mongoose an object modeling tool.

Now when you use the collection, you'll get better type support for for all the collection methods. Note that I had to make the _id required on the schema. If you make it optional, you still get a type error. The node driver team is working on this and other issues related to the type of _id in this PR: https://github.com/mongodb/node-mongodb-native/pull/3077

To communicate with MongoDB database we will need Node driver mongodb. So install it.

Could this _ensureIndex be the problem? I think that may be calling into listIndexes here: https://github.com/mongodb/node-mongodb-native/blob/2b18411d2f57e06d11262d5a308c56a9f561789e/lib/operations/db_ops.js#L305. IIRC, ensureIndex is deprecated, and you should use createIndex instead. I'm not familiar with meteor, so I'm not exactly sure what that code looks like, but the README shows how to access the underlying MongoDB driver directly: https://github.com/meteor/meteor/tree/devel/packages/mongo#direct-access-to-npm-mongodb-api. Hope that helps!

pg doesn't do too well with serverless, dead connections are left in the pool (or something)

https://github.com/brianc/node-postgres/issues/2112

If you don't want to use ORM then there are some other packages as well! For PostgreSQL we have node-postgres

Interface with PostgreSQL database

(Instead of the following with pg.)

So far every JS framework that uses https://node-postgres.com works great and so no reason to think Drizzle wouldn't.

One thing that keeps coming up is that SQL equals low productivity. I don't think this is true. I think the culprit is that most developers are using to heavily abstracting SQL using ORMs like Prisma that hides the database and SQL logic.

Since building a SQL generator (https://aihelperbot.com) as a side project, I have become much more proficient in SQL and even though I am also locked into Prisma, I use the `queryRaw` all the time to execute raw SQL queries. You can understand the code without knowing Prisma API. It is more performant. For more complex SQL queries, I use the SQL generator for initial suggestions and adapt if needed.

For the next projects I build I want to use the minimal Postgres client (https://github.com/brianc/node-postgres) combined with a lightweight migration library.

For newer projects I use the small Postgres client. Initially my leap into SQL was lead by AI but as I refreshed and relearned SQL, I now use a mixture of AI and self-written SQL queries. Something like this is just easier to have AI do the grunt work and then adjustment as needed.

This was a known issue for pg developers, and they managed to fix it a long time ago (at the pg level), but the knowledge of this problem didn't reach Knex maintainers.

Integrate the database into your application itself with a postgres client library allowing your applications to make infrastructure changes (like provisioning sharded resources for a client that wants isolation, or using a more accurate forecasting model to pre-allocate more resources before the storm hits).

node-postgres (raw sql, without ORM)