aws-lambda-runtimes-performance VS MongoDB

> NodeJs is the slowest runtime, after some time it becomes better(JIT?) but still is not good enough. In addition, we see the NodeJS has the worst maximum duration.

The conclusion drawn about NodeJS performance is flawed due to a quirk of the default settings in the AWS SDK for JS compared to other languages. By default, it opens and closes a TCP connection for each request. That overhead can be greater than the time actually needed to interact with DDB.

I submitted a pull request to fix that configuration[0]. I expect the performance of NodeJS warm starts to look quite a bit better after that.

[0]: https://github.com/Aleksandr-Filichkin/aws-lambda-runtimes-p...

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!