MySQL VS MongoDB

But there's another approach: wrapping tests in transactions and rolling back the transaction after each test completes. This approach isn't exactly new - it's used in other languages and platforms like Ruby on Rails, Laravel, and Spring - but it's rarely implemented in Node.js projects. In projects I work on, MySQL with various ORMs/query builders is commonly used, but I didn't want to write transactional test implementations for each library, and in some cases it's impossible due to their API specifics. The solution was found by recognizing that most ORMs and query builders use one of two packages, mysql or mysql2, as clients. Therefore, it would be sufficient to patch these drivers to add support for transactional tests for all libraries using them.

Well the mysql package has been around 13 years.

Hmm... I'm not sure why you get a "Loading..." I don't even remember adding a "Loading..." so I'm not sure what that's from. Yes, I do have a account system in place using a database. I am using Node.js and have a mysql backed account system. It requires a bit of setup to get MySQL running on your machine (depending on your operating system), but it's super easy to use on your local system if you have the environment setup. It's a bit more challenging once you take it online; I have a digital ocean droplet that's running this service and a couple more personal projects as well, which does come with a cost to have online. But at least using locally you can build something for free and then when you want you can take it online.

mysql package does not support MySQL 8 authentication method (More info here)

However, if you wanted to use js to interact directly with db then a framework like express would not be necessary. You’d just use a database connector that’s specific to the type of database you’re using. for example

MongoDB supports 3 possible network compressors: zlib, ZStandard (zstd) and Snappy. zlib is always supported out of the box, however some drivers may require an additional package to support additional compressors. For example, when using MongoDB's Node.js driver, the following would be required from npm to support snappy and zstd:

Let's assume your application uses v4.17.2 of the MongoDB Node.js driver, but your application has been humming along for some time without issue. You got an email indicating your cluster was going to be upgraded from MongoDB 6.0 to MongoDB 7.0, but based on the driver compatibility table that version of the driver isn't even present!

I mean, this really depends on what you're looking at.

Here's a sample from the MongoDB client: https://github.com/mongodb/node-mongodb-native/blob/main/src...

Here's a sample from Storybook: https://github.com/storybookjs/storybook/blob/next/code/core...

Here's a sample from Prisma: https://github.com/prisma/prisma/blob/main/packages/client/s...

Here's a sample from Cal.com: https://github.com/calcom/cal.com/blob/main/packages/core/Ev...

It's rather the specific use case that determines the style of the code that's written. In the examples above, there's no need for the teams to choose JavaScript classes and inheritance to model the logic, yet it likely better fits the programming model of those modules.

Look at Nest.js as well: https://github.com/nestjs/nest/blob/master/packages/core/rou...

The whole codebase of Nest.js looks an aweful lot like Spring or ASP.NET (controller syntax) probably because there's a lot of crossover in terms of what APIs need at scale.

It just so happens that most use cases for C# and Java favor applications at a larger scale. Another key difference being object scope and lifecycles -- something that rarely comes into play in the generally single-threaded Node runtime. This being one of the key reasons why dependency injection is a thing in C# and Java land.

The Node.js callback pattern is ubiquitous and familiar, resulting in many popular libraries such as the MongoDB Node.js driver adopting it as well.

Given the example above (using the Node.js driver) the specified connection events and command events would be logged as they’re emitted by the driver:

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