NodEnd

MERN STACK DEVELOPMENT

[nodejsdevelopment]

Famous Cities Nickname | Sobriquets Of World | Complete List

[nodejsdevelopment]

Never underestimate the efforts of students during exam season. 🤣

[nodejsdevelopment]

[nodejsdevelopment]

[nodejsdevelopment]

What is NodeJS? Pros | Cons | Usage

By understanding a new concept, we start from the beginning. In website development, we use basics which are HTML, CSS, and Javascript. HTML (HyperText Markup Language) helps to put content on pages which you are now reading now, while CSS (Cascading Style Sheet) used to design and beautifying web pages like Images, font size, color schema, etc and Javascript is used to handle the behavior of web pages:

1. Client-Side Javascript

2. Server-Side Javascript

To run the Javascript code we used a text editor to write code and save it with the .js file extension. And saved file must be added in the HTML document head tag by using the script element with source attribute. Therefore we need a browser for running this code. Browser is Javascript code runtime, but we take Javascript code out of the browser and execute. Here comes NodeJS helps to run code outside the browser.

The official NodeJS definition is "It is a javascript runtime built on Google's open Source V8 engine."

Actually, NodeJS is another Javascript runtime. It is just like a container or as an environment.

But, who actually executes the code if not the browser?

Here comes the V8 engine developed by Google. It implements Web Assembly and ECMAScript.

To read more about ECMAScript click the below link:

What is an ECMAScript?

NodeJS Pros:

1. Single-threaded, based on event-driven, non-blocking I/O Model.

2. Perfect for building fast and scalable data-intensive apps.

3. Fullstack Javascript serves both client and server-side applications.

4. It saves money and time by hiring only one developer instead of the front-end and back-end developers individually.

5. Very easy to learn with strong documentation.

NodeJS Usage:

1. API with databases behind it. (Preferably NoSQL)

2. Real-time chat applications.

3. Data streaming. (Think YouTube)

4. Server-side web applications.

Do Not Use:

Application with heavy server-side processing.

Scope of NodeJS:

Companies like Netflix, Uber, PayPal, eBay have started using NodeJS in production. It has a very active developer community. It has an NPM huge library of open sources.

[nodejsdevelopment]

FRONT-END VS BACK-END: What is the difference?

We consider client-server architecture to distinguish between the front-end and back-end of a website, as well as web development in general.

Front End Development:

Front-end development refers to everything that occurs within a web browser. As a result, the name front-end refers to the process of planning and developing the final website that will be visible to the user. The basic technologies used by front-end developers are HTML, CSS, and JavaScript, which together make up the front-end technology stack. Many current front-end developers now use React, Angular, Redux, and GraphQL as part of their front-end stack. As a result, these technologies facilitate front-end development. Now we'll look at the back-end.

Back End Development:

The back-end of web development refers to everything that occurs on the web server, or everything that is not visible to the end user, hence the name. And, since we're on the subject of servers, let's take a moment to define what a server is.

A basic server is simply a computer linked to the internet that stores a website's data such as HTML, CSS, and JavaScript, and also runs an HTTP server capable of comprehending URLs, requests, and responding to them. This piece of HTTP server software is what sends and receives requests and responses from the browser. As a result, it functions as a link between the front-end and back-end of a website or web application. Because all a simple web server can do is provide static files to clients through HTTP, it's now known as a static server. If all you need is to host a simple website, this is all you'll need. However, if you want to take it a step further and construct dynamic web applications that talk to databases and other cool stuff, you'll need a server that can execute dynamic applications as well. This is referred to as a dynamic server, as it contains an app, an HTTP server, and, of course, files that communicate with one another. And while that may be all we need for some applications, most dynamic websites or apps will also require the use of a database, which we may access directly from applications. The database can be used to store information such as users, application data, or text to populate a website design. A database will always be present in every significant application, and back-end code will interface with it. So, some common tasks handled on the back-end, or server side, include creating user profiles, logging in, sending emails, processing payments, retrieving and sending request data from a database to a client, manipulating data in the database, filling out website templates, and so on.

There are a number of various back-end technologies and stacks to choose from. PHP with a MySQL database, Python with a PostgreSQL database, and Ruby on Rails are just a few examples.

Full Stack Development:

You may have heard the term "full stack," which simply refers to the front-end and back-end stacks combined. As a result, a full stack developer is someone who works on both the front-end and the back-end of a website. However, full-stack developers are becoming increasingly rare, especially as the front-end is becoming more complex.

If you feel difficulty between Static and Dynamic Website?

leave a comment "Yes", we will post an article on it too.

Is this helpful?

[nodejsdevelopment]

How NodeJS works behind the scene?

let's start by learning a little bit about Node working. So let's represent that structure in terms of Node dependence, which is a few libraries on which Node depends for efficiency. Node operating time, therefore, has several dependencies, and most important:

V8 engine

libuv

Node is a JavaScript run time based on Google's V8 engine, right? And then, that’s why it seems as a dependency. If it were not for the V8, Node would have no way of understanding the JavaScript code.

What is V8 engine?

And of course, the V8 is an important part of the Node architecture. Also, the V8 engine is the one that converts JavaScript code into machine code that a computer can actually understand.  And the V8 itself is written in  C ++ code. But that alone isn't enough to create a whole server-side like Node. And that’s why we also have libuv in Node.

What is Libuv?

And libuv is an open-source library with a strong focus on asynchronous IO.  This layer is what gives Node access to a working computer program, file system, communications, and more. The important thing to note is that libuv is actually written entirely in C ++ and not in JavaScript. Apart from that, libuv also uses two of the most important features of Node.JS:

The event loop

The thread pool

And in simple terms, the event loop is responsible for handling simple tasks such as using telephones and network cables while the thread pool is for heavy work such as file access or compression or something like that. Node itself is a program written in C ++ and JavaScript and not just JavaScript. Now the beauty of this is that Node.JS binds all these libraries together, whether written in C ++ or JavaScript, and gives developers access to their works with pure JavaScript. So it really gives us a really good layer of extraction to make our lives a lot easier instead of liking dirt with the C ++ code. That would be a terrible thing, wouldn't it? So again, this build allows us to write 100 percent pure JavaScript code, working with Node.JS and still accessing functions such as file readings, background scenes actually used in libuv or other libraries in the C ++ language. And when it comes to other libraries, Node actually relies not only on V8 and Libuv, but also on the HTTP-parser to split HTTP, ic-ares, or something similar for certain DNS application objects, OpenSSL for Keepography, and compression.

So at the end, when all these pieces fit together properly, we end up with Node.JS ready to be used in server-side applications. And next, you'll learn more about the Node threads and the event loop.

So stay tuned for that.