← Course overviewFree lesson 1 of 3 · lesson 1 of 62Next lesson →

Unlock all 62 lessons of Everything about Database 2.0Full course ₹40,000 · paid

Price & syllabus
Free lesson · 17 min · no payment

Database Basics, Data vs Information and Single and Multi-Tier Architecture

A free lesson from Skill-Lync's Everything about Database 2.0 course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Module 1 - Database Introduction”

What will you learn in this free Everything about Database 2.0 lesson?

The instructor opens the database course by defining data, information, a database and a DBMS, using examples like a college database and website cookies. It places the database in a web application stack beside the front end and back end, names MySQL, MongoDB, Redis and Oracle, and contrasts single tier, two tier and three tier architectures.

  • Difference between data, database and DBMS
  • Where the database sits in a web application stack
  • Examples of DBMS: MySQL, MongoDB, Redis, Postgres
  • Single, two and three tier architectures

What comes after lesson 1?

The next free lesson is lesson 2, “Installing XAMPP, Creating a First MySQL Table and DBMS Components” (20 min). Later in Skill-Lync's Everything about Database 2.0 course (paid): lesson 4, Module 1 - Types of DB, SQL vs NOSQL; lesson 5, Module 1 - CRUD operation example in MySQL, OLTP, OLAP; lesson 6, Module 2 - Database design, ER model, Entity, Attributes. The full course has 62 lessons (19 h 22 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.

Hi, welcome to Everything About Databases course. I am so excited to begin this journey with you. In this course, we are going to learn everything about databases, how to work with databases, how to store data, how to retrieve data, and everything in an optimized fashion. We will learn so many different technologies and when to use what. So I am so excited and I hope that you are too. In this week, I am going to introduce you to databases and work on some extremely important concepts before we dive into designing them, working with them, querying them, and all of that.

So in this module, I am actually going to talk about where is the database in a web application architecture. We are also going to talk more about, you know, the whole database architecture, about data independence, about data models. I am also going to talk about the characteristics of a database management system, what should it be, how should it be, and what is the thing which we want really from a database management system. We will talk about some extremely important properties which are known as asset properties.

I am also going to compare storing data in databases versus in a general file system. We will look at, you know, the different types of databases which we have, and then we are going to actually, you know, talk about some DBMS languages. Specifically, what do we use for querying? That is the query language which we are going to discuss. I am also going to tell you what exactly is a schema and how would we ever create a schema for a database. What is a view of a database?

Then, how we could use the set theory which we actually learned in elementary mathematics to actually work with all of our data within the database. So, what's going to be our learning objectives for this week? We will learn about data and databases, database management system, its characteristics, the models, types, intention, and extension. You know, what are these terms? And, you know, how we could deal with data as sets. Now, remember that data is the new oil. And this is absolutely true because the wealth which we get in understanding users' data cannot be matched by anything else existing today.

We know there is so much of discussion about usage of data, data handling, data mining, and data privacy. And all of these things are extremely important because what we do with the user's data will really help us understand what is the thing which the users need. And when we understand what do the users need, we are able to actually create proper software systems for those targeted users. So, data is the new oil. Now, when we actually have to deal with, you know, any important thing like data, we would not just simply store it just the way we would store trash in a dustbin, right?

Because otherwise, if we want any important and relevant information from the data, we would be looking at it just like this. And we don't want to do that, right? We do not want to thoughtlessly look at data and not being able to understand relevant information from the data. We do not want that. What we want is to store the data in such a relevant manner that as soon as we want to derive some information from the data, we have it very quick and very handy for us.

And for that, we use database management systems. Now, what is data? Data is any fact that can be recorded and stored. It can be a collection of distinct units of information. So, any information, for example, you may think of, you know, your shopping list or personal information about you or property information about your family. Any confidential information, any public information, all those units of information, the collection of them is data. So, it can be also in various forms. For example, it could be on a text.

It could be numbers, you know, general phone numbers of your friends. That is also a data. It could be media. You know, your birthday party recording. That is a data. It could also be in simple byte form. Any form you could choose but have a meaningful information, that is data. And it can be stored on anything. It can be stored on paper. It can be stored on a, you know, memory device, on an electronic memory, anything. Now, what is a database? We know that, you know, we have this collection of data in, let's say, a phone book or our shopping list on a piece of paper or, you know, we would have, you know, a diary full of, you know, all the wishes which we have.

All these things are database. The Instagram user base, your previous school details, all these information, all this collection of related information, that is a database. Now, what's the purpose of database? The purpose of a database is actually to operate on a large amount of information. So, for example, you would keep your monthly budget or a company would keep their monthly budget in, let's say, an Excel sheet. And the reason for that is pretty simple because an Excel is going to help them operate on that large amount of information, derive extremely important information from that information of sales, of budgets, etc.

Just by using simple formulae on the Excel sheet itself. So, to operate on that large amount of information, they are using Microsoft Excel, let's say. And that's, you know, just the purpose of using Microsoft Excel. And that's exactly why we would use the database in a software system as well. Because we want to operate on a large amount of information of, let's say, our customers, on the goods which we have, on the inventory, or on the employees which a company has, and many other things. A database really helps us to store, retrieve, and manage data in the form of tables or creating reports, generating reports, etc.

In a database, data can be stored in different ways. As I said that, you know, anything written on a piece of paper in the form of a list or, you know, any relevant information can also be a database. It could be simply present in your mind, right? You know, all the names of people, all their backgrounds of your friends is stored in your mind. That's a pretty good database. Or let's say you remember so many, so many different songs. And, you know, whenever you are actually playing a game with songs, your mind acts as a database of, you know, all the songs which you know.

A computer can be a database of, you know, all the information you have stored in the computer in a relevant format. And your assignment files, let's say, you know, you do your course, you actually, you know, create your assignments. All those files are also a database of the study which you have done or the work which you have done within the course. Also, ad hoc things like the comment section in a social media website. That is also a database. It's a database of information from different users about what they feel about that particular post or video.

So all these things are databases in and of themselves. So remember that data is just some facts and some statistics which is stored or, you know, it is free-flowing over a network. But it's generally raw and, you know, unprocessed. For example, you know, if you visit any website, the website might store the user's data like IP address, what pages they actually, you know, accessed, any cookies which they obtained from, you know, the user's browser, what date and time did you actually go to that particular website, you know, your name, probably your, you know, any data which you might have entered within the website like your age, etc.

So now all that data is information that they can use and process and they can actually turn it to something meaningful for the next time you visit them. For example, they could store, you know, some information about you in a cookie so that the next time you visit them, they know that, you know, what relevant data is, you know, something which you are going to want from them. And a database is just a collection of related data. It has to be organized in a way that, you know, it can be easily accessed, managed and updated.

For example, there could be a college database which would, you know, organize details of all the students, their payments, their subjects, the admin of this college, the staff of the college, all the faculty members, their papers which are published, you know, everything related to the faculty, to the students, to the administration, to the examinations which they conduct. All of that information can be put in a database so that, you know, they're able to easily retrieve, insert or delete information. So it's just an organized collection of data that can be easily accessed and managed.

Now, you can actually, you know, organize all that data in terms of tables like rows and columns, you know, just like you might put it in an Excel sheet or you might use an actual database management system like MySQL, etc. These database handlers, you know, they create database in such a way that a set of software programs are able to access them. And, you know, you have all the various security measures just to make sure that, you know, database is not accessed in an illegal fashion because all your data, let's say, of your institute or, you know, your website or your company is pretty confidential, right?

So you need that kind of security. There are many database systems like MySQL, Sybase, Oracle, MongoDB, Informix, PostgreSQL, SQL Server, etc. So all these are modern database systems and we are going to study about many of them in this particular course. Now, what is a database management system or DBMS? It's a special software. MATLAB program for creating and maintaining a database. It manages various operations like database creation, storing data in database, updating data, creating a table in the database, etc. It also maintains consistency in the case that multiple users are using the same database.

So, for example, you have a particular database and let's say it has details of students and now you have, you know, multiple teachers actually working on the same database, they are updating the details of student. It may be that, you know, one teacher actually wants to add some marks of a particular student out of 100 and the other teacher also wants to do the same thing. But then what turns out is that the student gets more than 100 marks out of 100 in that particular subject just because both the teachers are given the task of updating the data of that particular student.

In such cases, when multiple users are using the same data, we really need to make sure the data is consistent as per the standards of the database. Also, it should be consistent for all the users accessing it. For example, I just saw that last month's sale was, you know, $1,000. It should not be that somebody else checks the database and now finds some other information about last month's sales because that has to be consistent for everybody, right? Until and unless the data of this month gets updated, which should actually reflect on this month's sales only, right?

So, any kind of inconsistencies within the database is not something which we want and database management system helps us in maintaining them. How does it help us? What are the mechanisms? All that we are going to see in this particular course. So, remember that a DBMS is just a software that would allow us to create, define, and manipulate database. It would also allow users to store and process and analyze data very easily. Database management system also provides us with an interface or a tool which will help us perform various operations like, you know, creating database, storing data in it, updating data, creating tables in the database, and a lot more things.

DBMS also provides us, you know, protection and security to the databases. It also maintains data consistency in case of multiple users. And as I said that, you know, some very common databases are MySQL, MongoDB, in-memory databases like Redis, and we are going to see about all of them in this course. A DBMS would also help us effectively store data and retrieve it with the use of efficient data structures to optimize dealing with very large amount of data stored in a permanent data storage device. For example, you would have your hard disk, you know, or any disk on the server.

Now, let's actually understand where is this database in our entire web application architecture? Because after all, we, being a full-stack web developer, need to know everything about every stack which we have in the entire stack of a web application, right? So, we have our front-end, which is, you know, the view which the user sees. And we have learned, you know, technologies like HTML5, CSS3, JavaScript. We also know that, you know, there are frameworks and libraries like Bootstrap, Angular, React, which can be used on the front-end.

Then we have the back-end or the middleware, because it sits in the middle, and it takes care of, you know, the back-end logic and everything of the website. And most importantly, our entire information is being stored in the database, which is at the last end of the spectrum of this entire stack. And this is where, you know, all of our important data has to be kept and persisted and made consistent for all the users around the world. So, as I said, we could use something like Oracle or MySQL or Postgres or MongoDB or Cassandra or any other technology which we deem fit for being a database of our web application based on, you know, how we want to retrieve and store data and how we want to actually use the data.

But the essence is that for any database, if we have a web application, we would be sending HTTP requests to get the data. And then, you know, in the form of an HTTP response, we would send the data back to the user on the front-end. We also have, you know, different API service providers whose service we would be using either on the front-end or, you know, in the middleware or while working with data. But in this course, we are actually going to work specifically on database and how best we can store data and how best we can use the modern technologies in making our website very, very fast and very, very responsive.

Now, your application architecture could be, you know, a single-tier architecture. You have your user working on the application, which is going to be the client. And then you would have your server, which would just be a simple database system. So, for example, your client directly wants database on the server. So, it may be that you just have an application which would open up an Excel sheet from the server and show all that data to the database. And that's a simple application, right? This application would help you access data in an Excel format.

And that's absolutely fine. It's a single-tier architecture application. You may also have multiple tiers, like you would have a three-tier architecture in which you have a client who's actually dealing with the web server. You also have an application server where your application is, you know, hosted. And you have your database giving information to the application server, which is now dealing with the web server and giving information to the front-end of your application. So, this is essentially a three-tier. So, you have the front-end, you have a back-end, and you have a database.

Now, remember that in this kind of basic client-server architecture, you would have your web servers or database servers and, you know, any of the components, they all are connected with the network. And your DBMS design would depend upon its architecture. In this single-tier architecture, the database is actually directly available to the user. So, the user can actually directly sit on the DBMS and use it. And this is something which I'm going to show you in this week as well. If the user does any changes to the database, it is directly done within the database itself.

And this becomes, you know, very handy for end users to directly work with the database you want to provide them. This kind of architecture is something which we, in fact, you know, developers use for our local application because that's where programmers can directly communicate with the database for quick response. But if you have multiple tiers, let's say, for example, you are not directly dealing with the database, you actually are dealing with the back-end language, which is in turn dealing with the database. That would become a two-tier architecture.

And if you have a front-end also, which deals with the back-end, which deals with the database, then you would have a three-tier architecture. This is how the architecture of a large-scale web application would work. It would have a front-end, it would have a back-end, and it would have a database, and each of them working with each other, and the user is not able to directly work with the database.

Want the rest of Everything about Database 2.0?

Get the full course syllabus and fees.

The full course is paid (₹40,000). We'll send the syllabus and call you back within one working day.

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.

Full course · paid

Unlock the full Everything about Database 2.0 course

The remaining 59 lessons, mentor-reviewed projects and a certificate come with the paid course (₹40,000). Leave your details: we'll send the syllabus and fees and call you back.

Get the syllabus and fees

A counsellor calls you back within one working day.

By submitting you agree to our Terms and Privacy Policy.

Grow by Skill-Lync · free lesson

Start watching

Free, no payment. Leave your details once and every free lesson on Grow plays straight away. A Skill-Lync counsellor may call you about the full Everything about Database 2.0 course.

By submitting you agree to our Terms and Privacy Policy.

Talk to a career counsellor

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.