Unlock all 53 lessons of Angular Web Development for the Real WorldFull course ₹40,000 · paid
Angular Course Overview, Web Basics and Developer Roles
A free lesson from Skill-Lync's Angular Web Development for the Real World course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Week 1 Session 1”
What will you learn in this free Angular Web Development for the Real World lesson?
The session outlines the course and its prerequisites, then uses a whiteboard to explain how HTML, CSS and JavaScript build a website. It describes native, web and hybrid application types, the front-end, API and database developer roles, and a career path from Angular to full stack.
- Course scope and prerequisites for Angular
- How HTML, CSS and JavaScript work together
- Native, web and hybrid application types
- Front-end, API and database developer roles
What comes after lesson 1?
The next free lesson is lesson 2, “Frameworks vs Libraries and MVC, MVP and MVVM Patterns” (27 min). Later in Skill-Lync's Angular Web Development for the Real World course (paid): lesson 4, Week 2 Session 1; lesson 5, Week 2 Session 2; lesson 6, Week 2 Session 3. The full course has 53 lessons (25 h 59 min of video); see the course overview or its price and syllabus.
Lesson transcript
Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.
Hello everyone, I am excited to welcome you all on this course of Angular Development by Skill-Lync. This is the first session of the first week of this course. As part of this week, we will be covering the following main topics, which includes the introduction to this course, what are the prerequisites for digging up this course, what are the types of application and developers that are there around in the market, what is Angular, and also we will be covering upon an introduction to TypeScript. The main learning objectives of this week is, we will try to understand what is front-end web development and what are the various frameworks and libraries and patterns which are used in front-end web development.
This will clear your concepts and also make you understand the various terminologies and jargons that are used, commonly used in front-end web development. Also, we would understand what is Angular and what is TypeScript, which is used to develop Angular applications. So, let's now understand what is this course all about. So, this course is a crisp yet detailed introduction to Angular, starting right from the fundamentals and we will be gradually moving on to the advanced concepts by end of this course. We will be taking up real-world examples and also tips will be provided to you to bring you on par with experienced developers quickly.
So, since many of you could be freshers who have little to no experience on Angular, by taking up this course, you would be on par with any of those experienced developers by end of this course. Also, we would be doing hands-on coding and real-world projects would be provided to you to help you get a flavor of Angular development while you learn this course. Next, let's understand what are the prerequisites for taking this course. A basic working knowledge of HTML, CSS and JavaScript is mandatory to learn this course effectively because we would be using all these three extensively across all the projects.
Also, you should be able to understand how to create a basic webpage using HTML, CSS and JavaScript. Don't worry if you don't know them. You can go through the reference content and links which are provided at the end of this week so that you can understand how these three technologies work together to create any of those basic webpages. Also, you should have a basic understanding of what is an API, what is HTTP request, what is JSON, what is REST and how data transfers between the browser, backend, servers and the database.
Again, the reference links for this would be provided at the end of this week so you can go through them and brush up your concept. Anyways, for the benefit of students, let's try to understand what each of these concepts means through a simple demo using a whiteboard. So now let's understand what is a website all about. So website is nothing but say any web page that like you know you type in your browser say like you know www. A website could be any of the website that you type in your browser like say www.google.com So when you type any of this website, so predominantly what happens is all these websites are composed of three basic building blocks.
One is your HTML, the other is your CSS and the third is your JavaScript. And the fourth one which we may also add are your media files which could be your image, could be your audio, could be your video and all those kind of media elements that you see on the web page. So now let's try to understand what each of these actually mean. So let's take first the HTML. What is an HTML? So an HTML is nothing but it is just a markup language which provides you a layout of how your website looks.
So say for an example, assume like this is my website and I have the following elements. See at the top, I have the navigation bar which gives me a bunch of links like you know for home, for one of my web page to log in and here I have my logo of my website. On the left-hand side, I could have a like you know a sidebar which would list out a different kind of links or menus which I can click on. On the right-hand side on the central part, I could have a heading over here and then I could have some contents right below it as a paragraph.
Then I may also have a ad over here as a big banner. On the left-hand side, again, I could have a big image or over here and again at the bottom, I could have a bunch of other links with the user might click. So let's take this sample website as our simple layout for HTML. So as you can see over here, what we have essentially done is we have listed all the different elements or contents which are available for our website and using HTML, what we can do is we just define a layout which uses all these contents and places them as part of a markup language.
So as you may know, HTML looks something like this, right? So you start with HTML, then you have head, then you have your body. See, I'm not closing it just for the sake of this demo but just to make you understand like how a HTML looks. So just assume like you know, this is my sample HTML like a code. So inside this, what I do is I define a bunch of tags which would tell my browser on how my website should be rendered in terms of placement and you know, what are the various content which are available on this website.
So as I just to summarize it, HTML is nothing but you can just say that you know, it defines a container or defines a layout which tells your browser like you know, what are the various contents which are available on the website and where to place it. So now next, let's talk about what is a CSS. A CSS is nothing but it just gives some styling or like you know, makes your web page visually more enticing. So say for example, you might have observed in website like you know, there are animations that happens, you can color your fonts, you can place your content in such a way that you know, it could be on left, right, top, so on and so forth.
So all these effects are achieved by using the CSS. So CSS is nothing but cascading style sheets and the, it is the primary technology used for styling your website. So as you may know that any website is futile if you don't style it properly. So it is also necessary that you know, website contains proper CSS styling to ensure that it has the right styling mechanisms for the website to operate. The next part of a website is the JS or JavaScript. So what is JavaScript? So any interaction that you do with your website, it could be like you know, your click, your scroll or it could be like you know, you just navigate between pages and do any sort of interaction or basically I would say like you know, any sort of interaction that you have with your website.
Your JavaScript is responsible to ensure that it's able to capture those events and do some manipulation or give some output to the user. So I'll give you a simple example. Say when you scroll in your Facebook timeline, you would see that you know, when you reach at the end of your page, your browser automatically loads the next set of updates for you automatically as you keep on scrolling down. So this is achieved by using JavaScript. So you can see that JavaScript is what adds interactivity to your entire website.
So now that we are clear on what is HTML, CSS and JavaScript, let's try to just see it in action. So say now I go to a website like maybe google.com. So as I told you, HTML is what defines or tells this browser. So let's try to like look at the HTML of Google. So as you can see, this is what the HTML looks like. And when you click on each of this div over here, you can see that you know, it defines a particular section on your browser.
So as you can see that this defines the actual search bar, this defines the bottom bar, this defines the footer, this defines your header, so on and so forth. So as I said, your HTML is nothing but the placeholder that tells your browser on where to place each and every section or the content of your HTML. So the next part is the CSS. As you can see over here, your browser also comes with a bunch of CSS, which is nothing but this. So it defines like, you know, where your content should be placed.
What is the padding? What is the alignment? What is the color? So on and so forth. And let's see about JavaScript as well. So as you can see JavaScript, these are nothing but the JavaScript files, which are loaded when the Google is like, you know, rented or loaded by your browser. So just to give you an example as an and when I see when I click on this, you see a bunch of different suggestions which are coming in, which is achieved by using JavaScript. Similarly, when I type something, maybe like, you know, if I type in link, they can see over here.
Like as I type, Google is making call to the back end and fetching some data, which is relevant to what I'm typing and bringing all the relevant data over here. So this is what like, you know, is the utility of JavaScript. So now that we are clear with what is HTML, CSS and JavaScript. Now let's try to understand what are the other prerequisites or other terminologies which are used in this course. So the first thing is the API. So now let's try to understand what is API.
So coming back to the whiteboard, let's understand this. So assume that, you know, this is your browser or your like, you know, your web page that is being rendered and this is the Google server and this is the database. So I just first try to clear you the concepts on what are each of these. So your web server or your web, like, you know, the front end or the UI, which we call it, this is nothing but just a presentational layer. So anything that the user actually sees is on this part, which is why your google.com or any of those websites gets rendered.
And this is what is like, you know, being fetched by your browser and shown in your browser. So this browser, when it loads, say, google.com, skilllink.com or any of these websites internally, what it does is it communicates with the backend server of google.com, which is nothing. That they've been saved. But your API layer. And API is nothing but an application programming interface. So let's try to understand it in a simple way. So say when I load a google.com, the first thing that you see, let's go to the website and understand it.
So the first thing that you see is this is my static web page. But once I click on this, I see a bunch of like, you know, results or suggestions which are shown to me based on what I type. So you can understand this in a way that, you know, whatever user action he or she performs, there is certain data which is associated with that, which has to be fetched from the database and shown to the user. So the actual work of like, you know, mapping or fetching the data from this database and bringing it up back to the UI is what is being done by this API.
So in other simple word, I could say that API is nothing but the middleware or the bridge between your front end, which is your website and the back end database. So what it does is it is the, you can see the broker, which helps to take the request from the UI process it and like, you know, query or fetch the data from the packet and bring it back to the UI. Alternatively, you can also create and store new data into the database using API. One example could be like, you know, creating new user account.
In that case, you're not fetching any data. Rather, you're creating a data which is like, you know, transformed or validated by your API and then stored in your database. So this is what an API is all about. And database, as you may all know, is the storage where it actually stores all the data in several formats. It could be a table like your Oracle or Microsoft SQL, or it could also be a flat structure like your NoSQL, MongoDB kind of thing. So the major focus of our course would be the front end part, which was also called the front end web development, which can be done using a multiple frameworks.
And in our current course, we are going to do that using Angular. So now that we are clear on what is the API, let's also try to understand what is the HTTP request. So, so let's assume like, you know, this is your Chrome or your edge browser where you are loading your website. Okay, and this is your API server. So you may know that, you know, to communicate between this Chrome to this API, there should be a medium which should be able to do it. Right.
So this is nothing but your HTTP request, which helps to further communication from your Chrome to your backend servers. And as you may know, this can happen either through internet or it can also be through your company LAN or WAN, whatever it may be. So what I mean to say is it this, if you see access something like Google.com, it definitely goes through your internet and, you know, it hits your API server. But also there might be cases where you might be hitting the server from your company's internal intranet.
It could be like, you know, maybe something like your employee information or your salary detail, HR detail, so on and so forth. In those cases, the SQL does not actually flow through internet, but there could be an internal intranet through which your browser is setting your API server and getting the information. And for to make this communication possible, we have something called the HTTP protocol, hypertext transfer protocol, which is used to enable this communication between the frontend Chrome and the backend API server. So I hope you are able to understand what we have learned so far.
So coming back to a slide, we have so far understood like what is the prerequisite to the course and what we are going to learn. So now let's try to understand how to learn this course better. So I would strongly suggest that you pay attention to the topics that are being taught in the class, but also understand the coding exercises which are provided at the end of each week. Also in parallel, try to make your mini projects as well based on the knowledge gained in this course.
I'll try to explain this. So say for example, in a particular week, you learn about a new feature of Angular and though definitely we would be doing the corresponding coding exercise as well. I want you to also try in your own spare time another project which is based on the application of this, whatever you have learned in the class. So this will kind of cement your knowledge or like, you know, enhance your knowledge on Angular and it will really help you to like, you know, get pretty hands on with Angular.
The third point is nothing beats sheer practice done out of your passion. So what I mean by that is, as you keep on practicing and improving your skills and also do it passionately, there's nothing that which can substitute this. You'd really become a ace of whatever you're doing. And finally, do go through all the reference links and contents which I shared at end of each week and make sure you understand the concepts even better. So since due to the time restriction, we may not be able to cover each and every point, but what I will do is I will also share you extra links or materials at the end of this each course or each week, wherein you can explore those in your free time and try to understand better the different topics better.
Hello, everybody. Welcome to the second session of the week one of Angular development. As we have covered, what are the prerequisites and the basic introduction to this course. Now, let's now dive in and understand what are the types of application and developers that exist. Before we dive in further, there are a few must know concepts or terms or jargons, whatever you call them, that you must understand before delving into the world of web development. They are as follows. Like first is, you should understand what is a web versus what is a native versus what is a hybrid application.
Then next, you should be understanding what is a progressive web application. The third, you should understand what is a spar single web page application. Next, you should understand what is a front end versus what is a back end versus what is a full stack developer, which you often see around in any of the job search portals. And finally, we must understand what is a framework versus what is a library and which are used for building any web application. Next, we will also understand why we need any of these frameworks or libraries when we can develop any website using just HTML, CSS or JavaScript as we saw earlier.
And also, we would understand a key question that is frequently being asked like which framework or library is better for web development. So, first, let's try to understand what is a web versus native versus hybrid application. So, starting with web application. Web applications are nothing but the classic websites that you access from the web browser of your computer, mobile, TV, tablet or any of those modern devices. An example could be google.com, irctc.co.it or any of those normal websites which you access regularly from your mobile or laptop.
Any website or web application from a management or a developer perspective is easy to create which leaves dependence on hardware and is also easy to access anywhere for end user. What I mean by that? So, say if I have to develop a website, I don't really need to bother like, you know, what is the hardware or what is the specifications of the end users, computer, mobile, laptop or whatever put to develop it. Because a website runs independent of the hardware on which it is being executed.
All you need is just a browser and once the browser is installed, you can access any of the websites through it. Also, to develop a website, you just need a single code base to render it on any type of browsers or devices. For example, you can have the same code or the same website which can render on your laptop. The same website with the same code base can render differently on your tablet and the same website or web code can render differently on your mobile devices, which is called as responsive web application.
So, what is a responsive web application means using the single code base or single code setup, you are able to render your website differently across different screen sizes. So, let's try to understand this using a simple example as we go across. So, next, we will understand what is a native application. So, native applications are nothing but the mobile or the desktop applications that run from your desktop or mobile devices directly after installing it from maybe an app store or websites directly. So, an example would be your calculator on your mobile, WhatsApp that you use on your mobile, could be games like Angry Birds, so on and so forth.
So, usually native application provides the best user experience and performance among the other two applications. And why I say that? Because native applications are compiled by the specific operating system and it is optimized to use the hardware of that particular machine on which it's been run. So, what happens is if code is optimized for the hardware on which it's running, so the end user gets the best experience and also the performance. But, one point which needs to be remembered over here is that for native application, you need to have a separate code base for each platform.
Meaning, if you want to have an application for Android, then you need to maintain a separate code base. If you need to have an application for iOS, then again a separate code base. And if you are planning to develop a Windows program or application, you should have a different code base for it. So, the next is hybrid application, which I would say is the best of both worlds of web and native. So, they are nothing but the mobile or desktop application that run from your laptop or mobile devices directly after installing it in the app store.
But, instead of getting compiled into the native code, they use your device web browser to render the application. An example of this would be your Twitter, Uber or Instagram application that you download from app store. So, the basic advantage of using hybrid application is that it provides the best of both worlds. Like, it provides the flexibility of web application and also it provides you a few performance improvements over native application in a single code base. So, one thing to remember is that in a hybrid application, though you are having kind of a native application which is getting deployed in each and every hardware or like, you know, devices or operating system.
But, still you kind of have only a single code base which manages all these things together. So, now that we have tried to understand what is web native and hybrid application, let's have a simple demo to understand it. So, let's start with your web application. So, as I said. And like, you know, if you go to any of those websites, like say, google.com. So this is my google.com. So this is nothing but a web application. And why I call it a web application? Because I'm accessing google.com directly from a browser without installing it anywhere, right? And the same google.com can be opened across any device. Say, for example, if I have a mobile that has a browser, I can access this google.com over there.
Similarly, if I have a TV or any of those devices which have a browser installed and connected to internet, I could directly go and type in google.com and this page loads, right? So this is the advantage of using web application. And also we saw a term called responsive web application, right? So let's try to understand what is that. So say, assume like, you know, this is my full screen and, you know, this google.com is rendering properly. But what if I reduce the size of my screen just to imitate a mobile screen?
You can see that, you know, the same google.com still works fine on the smaller width as well. And why this is so is because using just a single code base, I'm able to kind of design or code my application in such a way that depending on the screen width on which it's being rendered, the application automatically adjusts all the content and it loads properly. So this is nothing but the concept of responsive web design. Now, let's try to understand what is a native application. So on your mobile, you have something like, like, you know, say calendar or calculator, WhatsApp and those kind of applications, right? Those are nothing but your native application.
So what is a native application? Even on Windows, for example, right? If you see, if you just go to start, you'd see a bunch of applications. So these are nothing but your native application. So say if I go and open calculator, this calculator is not written in HTML, CSS, JavaScript, but rather it is written in one of the languages which is supported by Windows, maybe like ASP.NET or C Sharp and gets compiled into the binary code, which is then executed on this Windows operating system. So a native application, as I said, is an application which is written on any of the programming language, which is supported by the underlying hardware or operating system.
And this gets compiled into an binary code, which then gets executed by your operating system, right? And to run this native application, we don't require any of this web browser or web rendering engine, right? So the next is the hybrid application. So to understand hybrid application, what I would do is let's try to understand it using the whiteboard. So as I said earlier, for a web application, it's important that, you know, you have something called a browser, right? And for a native application, it is important that it gets compiled to the default binary code, which is required to execute in the particular hardware, right?
So this is for native and this is for your web application. Now, in case of hybrid, what happens is it just sums up both of this and to make it faster for the developer to develop separate application for separate OS. I will tell you what it means. So assume that this is our mobile, OK, for which we are developing a native application using hybrid. So what it does is your hybrid application and hybrid application can be done using a number of technologies like Ionic, React Native, Flutter and so on.
So what it does is there will be an engine or like, you know, you can say a compiler visits in your application of that particular technology, which you're using. And internally, what it does is it uses the web browser of your underlying operating system to render your application on your screen. So the advantage of this is, though your application is compiled into a binary code, internally, it still uses the web browser of your particular operating system or hardware to render that particular web page on your screen.
So the user might get an, you say, experience of a native application, but internally, you are still using the browser of that particular operating system to render that website. See, a major advantage of using hybrid is if, say, you want to host your application in Play Store or Apple App Store, I don't know, you don't really want to have separate code base for each of this place to marketplaces. You can go with the hybrid approach first in case your application is not using too much of hardware features like camera, GPS, mic, phone and so forth.
And also it's not have is too much graphic intensive. Say, for example, you're not developing a game, it's just a simple application, like, you know, maybe a simple example would be like, you know, say you have a timesheet entry app, where in like, you know, your employee every day just comes in and, you know, enters a timesheet. So in those kind of scenarios, you can go with a hybrid application, where in like, you know, you can simply develop the application using a single code base using HTML, CSS and JavaScript or any of those frameworks or libraries that you are aware of.
And then compile it into a binary code, which can be deployed into any of your Android, iOS or Windows based devices. So coming back, let's proceed further. Next, we'll try to understand what is the progressive web application. See, a progressive web application is also a type of web application that is built with the intention of being more platform specific with capabilities and reliability. So for example, it would be Flipkart, Forbes.com and so on. So what is the advantage of using a progressive web app is? Say, they kind of mimic your native application.
So in your native application, if you're aware, you don't really need internet all the time. Say, for example, you take your calculator or your calendar, even if there is no internet, it kind of stores some data offline. Say, for example, if I take your calendar, right, your calendar constantly syncs with your Google or any of the account that you have. But still, when I open my calendar application without internet, it still caches some of the old data and shows me for that particular day, what are my reminders or to do list, right?
So something like that is what progressive web application also tries to mimic. So it kind of tries to like, you know, you can install it on your home screen. It can run without network connection. It can provide some device capabilities like kind of like, you know, starting your web camera or recording your voice using microphone and so on and so forth. But the advantage is like, you know, you don't really need to install a full-fledged native application to do all this. But rather, your web application itself can behave like a native application using this progressive web app concept.
But understand that progressive web app is not like your typical native application or hybrid application, which can be installed from App Store or Google Play Store. Rather, it is directly installed from your browser. I'll show you an example. So now there is a site called Tagblitz. So if you just Google Tagblitz, you will see that, you know, there is a website called Tagblitz, which helps you to kind of code on the go. Say, for example, I choose Angular over here. So without installing Angular on my local machine, I can quickly go ahead and, you know, kind of just try out Angular over here directly.
So it will start and browser for me. It will start like, you know, it will load up all the files for me. And, you know, as I keep on making some changes, you know, directly render that over here. OK, so if you purpose of showing you this was if you come, if you notice the browser over here, I get a icon called install Tagblitz. Right. So if I click on that, it will give me a prompt. Do I need to install it? So what it will do is in my browser itself, right?
And like using my Chrome browser, it just kind of mimics and native application opens a different window over here. As you can see, so this is nothing but still my Chrome window, but just slightly customized to give me a feeling of native application. So this is what a progressive web app is. So coming back to our topic. So next, let's try to understand what is a single page application. So single page application are nothing but a type of web application that renders all the dynamic component of the web application without reloading the entire page.
Thereby giving the end user a more refined experience like native application. And just to let you know that all the modern web application that we access today are mostly single page application. So just to give you a demo of this, let's go back to our browser. And let's try to open a site, maybe like, you know, say flipkart.com, which is a shopping site. So as you can see in flipkart.com, we have a bunch of different, like, you know, departments or categories from which we can access the website.
So let's try to like, you know, go to the grocery page. So as you can see over here, it is asking me to enter a pen code. Let me just enter a pen code or rather cut restarting. Okay. Now let's go and understand how the single page application works using a demo. So now let's go to google.com and here, let's just let me type skill link. Yeah. So as you can see, there are a bunch of different links that are available over here, right? So if I click on news or images or map or video, right?
You can see that it kind of instantly loads the entire application, but still the end user feels like, you know, they are still in the same application. As you can see, the Google or sign in these tab is not changing, right? So even if I'm like, you know, trying to click between different pages, the user feels like, you know, only the content here is being changed, but still they are being like, you know, staying in the single page. So that is the concept of single page application.
So coming back, finally, for this session, we'll try to understand like, you know, what is the front end versus back end versus a full stack developer. So front end developer is nothing but the developer who focuses on creating the end user facing screens, which is also called user interface or UI that you actually see on your web browser or on your native mobile application in your devices. So technically, a front end web developer uses HTML, CSS, and JavaScript as a base and any of the other libraries of frameworks like Angular, React, Vue, Ionic, HomeGar, React Native, Bootstrap, etc. to develop the screen.
For a front end web developer, the focus is more on user experience and journey in the application, right? So the next is the back end developer. So back end. There's nothing but he or she focuses on developing the middleware APIs and the databases that is required to keep our application up and running. So if the backend developer is the middleware-based backend developer who focuses on server-side, then they predominantly use Node.js, Java, or .NET, or Python, or any of the other languages for writing the APIs, and Oracle, Microsoft, SQL, or MongoDB, Postgres, or any of those databases for storing and retrieving and manipulating the data.
For a backend developer, the focus is more on implementing the business logic and other aspects of applications, which is fundamental for the success of application. So the next is full stack. And as you may assume, or like, you know, you can think about, it's nothing but, you know, they are the developer who can work on any part of a complete application, starting right from the UI, API, or the database as well. Usually, a full stack developer specializes in one stack of the application, like either they could be really strong on the UI, or on the API, or on the DB, and they know the other stacks fair enough to get the application up and running.
So there are a few common full stack developer stacks that are available, like mean, or merd, or angular react with java, .NET, and sql. So what does mean is, mean stands for Mongo, Express, Angular, and Node, or merd stands for Mongo, Express, React, and Node. So these are a kind of like, you know, you can say a few permutation combination, which you can play with different technologies on each stack, and can create your application. So finally, let's try to understand this from a whiteboard. So now let's assume that, you know, you want to be a front-end web developer.
So on, in the front-end web developer, the major focus is on HTML, CSS, and JavaScript. So these are the fundamental technologies or languages that you would be using to create any of the web applications on the front-end. And along with that, there are a bunch of frameworks and libraries which you may use. An example of that would be Angular, or React, or there's something called as Vue.js, or it could be like, you know, some styling frameworks like your bootstrap, or there are something called like, you know, different other frameworks like material UI, so on and so forth.
So a front-end web developer is predominantly only bothered about, how do I make my application look and feel for the end-user? And using all these different technologies, they develop the front-end part of the application for you. So the next on the back-end developer or the, there are different names for that. You can call it back-end developer, server-side developer, or API developer. So what their work predominantly is, they create the APIs which we saw earlier, which are nothing but the application programming interfaces, which kind of interfaces from your DB to your UI, right?
So they sit in between. So their work is, they manipulate or fetch the data from the back-end and give it to the front-end. And similarly, they take in the request from the front-end, manipulate it, and query or write it back to the database. So that is what the API developer predominantly does. And for API development, you either use something called Node.js, which is written in JavaScript and easy for front-end developers to learn, or you can use any of those existing technologies like Java, .NET, or you could use Python, and so on and so forth, right?
There are a bunch of server-side technologies which are available to write your API code. And finally, the database developer is nothing but the developer who is concerned with storing, retrieving, and manipulating your data actually in the databases, right? So for that, we have two major technologies, which is either SQL or NoSQL. So in the SQL databases are your common databases like Oracle, Microsoft, SQL, then you have something called Postgres, so on and so forth. And on NoSQL, one of the famous NoSQL databases, MongoDB. And you also have other a bunch of NoSQL databases as well.
So a database developer's predominant work is to ensure that, you know, he or she is manipulating and, you know, storing the data in such a format that it is compliant with all the business rules and validations that is required. So with that being understood, I would give you a simple tip or like, you know, a simple career map for your path. So now since you're learning Angular, I'm assuming that you are interested on the front-end part of it, which is the UI, right? So once you have a very decent enough experience on the UI, the next thing that you could explore is the API and a quickest path to explore that is through using Node.js.
And why I say Node.js is because Node.js also uses JavaScript as I told earlier. And since you already know Angular, which uses TypeScript, which is nothing but a superset of JavaScript, you can easily learn Node.js and write your own API. And once you are comfortable writing your API and, you know, querying the database to like, you know, get and fetch data. You could also learn a bit of a database using a NoSQL database like MongoDB, which typically looks like a JSON, which is nothing but like, you know, the objects with which you would be manipulating the data on your Angular or Node.js.
So this could be a typical career path for you in case you decide to be a full stack down the line. But currently, since you're starting with Angular, so this is how you can go about with your career. And with that, we come to the end of the first session of this week. And I'm hoping to see you back in the next session shortly. Thank you.