Full-Stack Roadmap (tutorial) [part-1]

This blog is a detailed summary of the full-stack roadmap. Completing the assignments will grant you access to the "internal-group" in Discord !

Apr 18, 2023

1. Why Full-Stack

Full-stack developers have a diverse range of skills that allows them to work on different parts of a project. They have a solid understanding of both, front-end technologies like HTML, CSS, and JavaScript, as well as back-end technologies like databases, servers, and APIs. This means that they can take on different tasks within a project, making them valuable team members.

Being a full-stack developer opens up more job opportunities. Many companies are looking for developers who can handle multiple tasks and technologies, and having experience in both front-end and back-end development makes a candidate stand out from the crowd. This also allows full-stack developers to work on a variety of projects, making their work more interesting and engaging.

2. Knowing the Basics

Communication Protocols
Communication protocols refer to rules and standards governing how data is exchanged and transmitted between servers and other network devices. There are many kinds of protocols but we’ll be sticking to two types for now

1. Transport Layer Protocol: The famous protocols are TCP (Transmission Control Protocol) and UDP (User Datagram Protocol)

2. Application Layer Protocol: example HTTP (HyperText Transfer Protocol)
We are focusing on HTTP for the scope of this very part of the roadmap. After following through the roadmap you will be able to see HTTP requests going out from the browser to the server.

We won’t be writing an HTTP server from scratch, since this is a very popular use case many libraries let you create an HTTP server in a few lines of code, and we would be using one such framework
Database
A database is a structured collection of data that is organized and managed in a way that enables retrieval, storage, and manipulation of data by backend applications or services. There are many popular databases out there such as:
Postgres, MongoDB, MySQL, Firebase, etc. We would be going with Postgres
a basic idea of how this system works
Messaging Buses / Pubsubs
to understand this better, let’s consider an example
After logging in to your Instagram account you receive a mail regarding the location the login was made from, the action of sending an email after you click on the log-in button is not as important to be considered to be on the backend-server, here we use asynchronous communication, asynchronous communication talk to the HTTP server rather than the browser, in short, these are used for the processes you worry about not immediately.
(The request to the messaging bus/pub subs is not an HTTP request, even if the email-service server is down it will eventually come up and pick requests from the messaging bus, since acknowledgement of whether an email has been sent or not is not necessary, HTTP is not used.)