DEV Community: ricahcyuzuzo

Evolution of MERN Stack

ricahcyuzuzo — Sun, 01 Mar 2020 15:41:27 +0000

MERN Stack

The MERN Stack is the javascript that is increasing more faster than any stack ever. This stack has a group of technologies that one takes its role and they are very important in their tasks.

Technologies

There are 4 Different technologies in the stack which are MongoDB, Express, React and Node.

React is a front-end Javascript library that is moving fast to the end line of developer's hearts, It was developed by Facebook. It came to existence in 2011 by a software engineer called Jordan Walke. At that time, The React crew and Facebook decided to make it an opensource in May 2013 at the JSConf US.

In 2015 at the JSConf, They announced the React Native that helps to develop mobile apps on different Operating Systems such as Android and IOS.

MongoDB is a NoSQL database that is fast in performance and it is also bringing more applications to life, and it very reliable.

Express is also a library that works on the Backend and it is also becoming more popular.

Nodejs is the technology that holds the Backend and it works well with Express.

In my opinion, I would advise everyone who wants to go far with javascript, they could go with the MERN Stack because it is awesome.

                                    -- Happy Coding --

The challenges I faced and solutions of my remote work journey so far

ricahcyuzuzo — Mon, 27 Jan 2020 15:37:06 +0000

Hello There, I'm Richard NSHIMYUMUKIZA. For this blog post, I'm going to share with you my experience with the first remote work I've ever done, it was so interesting. Deeply I will talk about the challenges I personally faced and even the solutions. Keep reading...

The Challenges I faced!

Most of the time, when we learn new things that we don't know, it becomes bored somehow, it becomes difficult when you start working in the way you were not familiar with. So, there are many challenges I faced!

The Internet

This is the biggest challenge I faced, Normally internet is a service that is sold by many service providers. In Rwanda, the internet that can be used in remote work can be somehow expensive for those who don't have any source of income and (I am one of those!).

It was very hard to find money for enough internet.

The working Environment

We all know that a good environment can affect your productivity and that is a principal.
While I started working remotely I had a bad working environment and affected my work.

In the first time of my remote work, I used work from my room at home but the desk setup and enough light didn't allow me to work convenience and be productive.

People around me.

It was so hard to tell people around me that I am doing my work. most of them used to know that when you have a job or any certain work you have to go to the office and there are hours to start and others for leaving the office, In my neighborhood there are few people know that someone can work at home.

The solutions!

Internet

This is how I solved the problem of the Internet, I went to a place that has fast free internet. In Kigali city, there is a place called Klab, and that place is good for those who want to learn and work remotely so if you are in Kigali city I recommend you to join that place, it is so good.

The working Environment.

To get the working environment, it took me also to get the Klab I told you above and there is a good place and it has a good working environment, there is a small cafeteria and also it is a quiet place, so to me it was a good environment.

People around me.

It took me time to convince people about what kind of work I do, and how I do that work, Something that helped is to tell them how the remote work is like how you can accomplish your work and reach out a message on a phone or send the work on WhatsApp in order to let them Understand that kind of job, which you can do wherever you are.

It was a pleasure to share with you how my first remote work.

                          -- Chills --

My Understanding of Event loop in Nodejs

ricahcyuzuzo — Wed, 22 Jan 2020 08:54:55 +0000

The understanding of event loop in Nodejs will first have to start with Knowing about the Threads, The thread can be seen as the a unit of operations the CPU has to do for us. One single program process can contain many Threads.

Using the below image to get an idea about the threads.

The Event Loop

When you run a node program, automatically the thread is created, That thread is the place where the codebase is going to be executed, In that thread, the Event loop is generated, The role of this loop is to schedule which operations our only thread should be performing at any given point in time.

Note This: the event loop does not get generated instantly as soon as we run our program. It only runs once the whole program has been executed

Let me explain in details

I will just have to assume that I have a program file to run in Nodejs 'programFile.js'.

We can run 'node programFile.js'.

The This is, in order to understand what is being done by the event loop, the picture below is showing how things are going during the event loop tick.

Step1: PerformChecks

has a specific condition that will determine if the loop needs to iterate again or not. Every iteration of the event loop is called a tick.

Conditions for Event loop to do a tick.

we execute our program, we will have a series of operations that need to be performed. These operations can be split into three main types:

Pending timer operations (setTimeout(), setInterval(), setImmediate())
Pending operating system tasks
Pending execution of long running operations

So, whenever one of those are pending the event loop will perform a new tick!

Step 2: Performing a tick

For every loop iteration, we can distinguish the following phases:

Phase 1: Node looks at its inner collection of pending timers and checks which callback functions passed to setTimeout() and setInterval() are ready to be called in case of an expired timer.

Phase 2: Node looks at its inner collection of pending OS tasks and checks which callback functions are ready to be called. An example of this could be the completed retrieval of a file from our machine’s hard drive.

Phase 3: Node pauses its execution waiting for new events to occur. With new events, we include: a new timer completion, a new OS task completion, a new pending operation completion.

Phase 4: Node checks if any function related to pending timers related to the setImmediate() function are ready to be called.

Phase 5: Manage close events, used to clean the state of our application.

                                --End--