GridFS | Simple GridFS capabilities | Runtime Evironment library

I am able to connect successfully with only selecting node 2.2.12 or later option from MongoDB atlas account.

And the string uri is as like below:

Node.js 4.4.4 is absolutely ancient.

It doesn't even show up on this page of releases, which says in part:

After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to Active LTS status and are ready for general use. LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.

Version 4.4 is well beyond its maintenance window, and I strongly urge you to upgrade this project.

Having said that, there's a good chance you can get Heroku to run Node.js 10 to match your local version. Heroku only officially supports the current and active LTS releases, but it doesn't prevent you from using older releases:

Since Heroku is based on a standard Ubuntu Linux stack, you can run most Node versions (>= 0.10.0) on the platform. However, the testing and support focus of the buildpack will be oriented around active LTS and Stable releases.

Update the engines section in your package.json:

MongoDB is not a good place for storing files. If you want to store files, you should use storages like Amazon S3 or Google Could Storage.

The good practice is to store the files in a storage and then to just save the URL of the uploaded image in the MongoDB.

When it comes to Node.js and Express, I would suggest multer package middleware, which is primarily used for uploading files. If you would use Amazon S3 for a storage, there is also a plug-in multer-s3 package that can be helpful.

You can check this video on how to configure Multer and implement image upload on your Node.js server. Once the image is uploaded, Multer will return data to you with destination field included. You can then save that destination in the MongoDB.

Because you use for loops the images will load one after the other instead of all at once, the loop will iterate then await then iterate again and await and so on.... You need to fire all async actions at once and await for all of them to finish, Promise.all using Array.map is a way to do it. Try something like this:

in the template, just add the properties:

edit: Buffer.from is not needed, as it's already a buffer:

with for loop:

Ok, I finally find a helpful answer to my question on this other question:

Creating a BLOB from a Base64 string in JavaScript

Here, the GridFS binary which is a base64 binary is converted in to a Blob object. Then the Blob object can be easily passed through the "URL.createObjectURL()"

The function to convert the base64 to blob is provided in the answer.

I hope this is helpfull for someone else.

You can use a middleware package like express-fileupload to handle file uploads. Here is the documentation for the package Link.

Assuming the name of the input for the image is image, you can access the image's information from req.files.image. This object contains the file represented in a buffer and its mimetype. Now you can store these two information in the database like this:

GridFS is a specification for storing and retrieving files that exceed the BSON document size limit of 16 MB. GridFS is a convention implemented by all MongoDB drivers that stores binary data across many smaller documents. The binaries are split into the chunks and then the chunks are stored in collections created by GridFS.

Having said that, given the presented use cases i would highly recommend using media server for storage as given the application landscape, that makes a more economical, viable and scalable solution.

Having said that, I would generally, avoid putting BLOBs in the database if there are other storage options that cost less as using a database as BLOB store is generally not a cost optimised solution. Sure, there are valid reasons for storing blobs in the database, but given the application’s use case (it being media intensive), use the media server for file storage, and databases for data structures.

In such cases, It is often easy to get "cost unoptimized" with time. Plus the database size would grow exponentially with time, bringing it's own challenges with RAM (WiredTiger Cache) management.

All in all - if it was me - I would use media storage for BLOB intensive applications than relying on databases.

I have figured it out, you just need to pass the name of the bucket with the argument. like this, if your desired name for the bucket is custom,