It is a basic Nodejs application. The application receives a request and sends a data as a response to the client.
The picture above shows the overfiew of the application. We have various products that have many information.You can see whether to be organic, the price and quantity for each produts and for more detail you can click the detail button.
The product detail page shows the detail that related product as you can understand from the name. You can see the product where is from coming, what are the vitamins that it's has and the description. Also the add cart button exists to add the product to the shopping card (seeing the prices)
I got information from the Node.js, Express, MongoDB & More: The Complete Bootcamp 2021 course that instructor Jonas Schmedtmann. There is the link: https://www.udemy.com/course/nodejs-express-mongodb-bootcamp
Streams are used to process (read and write) data piece by piece (chunk) without waiting to read or write the all data therefore we get free memory and get time. Perfect for handling large volumes of data for example videos.
The above the table shows us kind of streams. Readable and Writeable are the most important streams. You can have a look at.
Below you can see some of streaming companies.
If we need reading a large text file from the file system and send it to the client then we can use the this code that includes 3 different solutions. Basically read the files from a server and send it to a client as a response.
This solution is fine but there is a problem. Node have to load the entire data into memory because only after that's ready it can send the data to a client but if we have a big file as a we have in the folder, the app will be crashed because Node process consumes resources very quickly.Therefore you can use it while using a small text file, you can't with a big file.
We can use the streams that are a efficient way to read or write a big file. The streams reads the data piece by piece and sends it as a piece of data to a client until the all data is loaded. But another problem appears, while using the streams the write operation doesn't as fast as the read operation and it's called backpressure. To fix the backpressure we can use the code which in the Solution 3
As we said, the problem was backpressure so we can use this solution 3 to fix it. Create a readable stream as we done before in Solution 2 , read and send the data into the writeable stream as an input using the pipe() function. It handles the speed of incoming data so we can fix the backpressure therefore this solution is the best efficent way.
I got the codes from the Node.js, Express, MongoDB & More: The Complete Bootcamp 2021 course that instructor Jonas Schmedtmann. There is the link: https://www.udemy.com/course/nodejs-express-mongodb-bootcamp
We can use the require module for three different uses
- Core modules
require("http")
- Developer modules
require("./develop")
If we create a developer modules should use "./" or "../"
- 3rd party modules
require("express")
From npm
If you want to send multiple value, you should use exports, otherwise if you can to send a single variable, you should module.exports
If we run the code that in caching.js you can see the output below
"Hello World" executed once because when we run the require module it reads the entire file and it also stored the module.exports into the cache then we can call many times the cache() function it rendered only "Hello from caching".
I got information from the Node.js, Express, MongoDB & More: The Complete Bootcamp 2021 course that instructor Jonas Schmedtmann. There is the link: https://www.udemy.com/course/nodejs-express-mongodb-bootcamp
If you use the nested callback functions so much then there can be a problem that is called callback hell. To fix the problem we use promises(ES6) or async/await (ES2017). In this project we have a txt file that is called dog.txt and have an API that is located on https://dog.ceo/dog-api. We get the data from API then write the data in a txt file.
A promise is commonly defined as a proxy for a value that will eventually become available.The promises said to us "Hey I will fetch the data from as you wish, promise you! I will be in "pending state"until the data is available if the process of fetching data is successful then I will be in "resolve state" otherwise if there is an error will be in "reject state". Besides, to consume the promises then() and cath() methods are used. But there is a better way that is async/await. Using async is better than the use callbacks functions to create a promises because after a certain time the promises can be more complex.
Async always returns a promise then we use await that means is "the calling code will stop until the promise is resolved or rejected". You can see the codes in the project.
Also in there multiple promises example, the classic way to read,write and get data.
I got the codes from the Node.js, Express, MongoDB & More: The Complete Bootcamp 2021 course that instructor Jonas Schmedtmann. There is the link: https://www.udemy.com/course/nodejs-express-mongodb-bootcamp