MySQL - Structure Introduction

The structure of a MySQL Backend can be designed however the administrator thinks is logical. There are few hard rules for how the structure has to be designed.

Front End/ Back End

With modern applications there is a “front” and “back” end. The Back End is the database and infrastructure that allows users to access data through a Front End which would be the web based interface or native application on their mobile device.
Database Servers

Database servers are either physical or virtual servers with an operating system installed and then the database software installed on the OS.
For the database to be accessed by a front end not only does the database need to be configured properly, but the OS needs to be configured for the proper firewall rules and permissions.
MySQL Schema

Database – is the highest unit in a database system. You can have a single database for your company, or many. Having separate databases can be useful for security and reliability. Separate databases can be connected to by a single front end.
Tables – contain the records in the database. Tables should store “like” data. Such as a Users Table, and a Parts Table.
Columns Name – is the name of the data to be stored such as “firstName”.
Primary Keys – Every record in a database table must be unique. A Primary Key is a unique entry for each record. generally the Primary Key column is setup to auto increment.
Rows/ Records – Are the individual Records that are stored in a table
Data Types – You assign a data type to the Column in a Table. Such as INT, TEXT, FLOAT. This means that an INT field will not accept “bob” as an entry.
Schema – is the design and naming convention in the database. A front end can not store data to a database if the
Storage Engine

DON’T TOUCH!!!
Storage Engines are the component of MySQL that actually does the inserting and sorting actions. There can be reasons to change the Engine, but generally just leave it as the default which is currently InnoDB.
Users

Databases have user accounts and permissions like other software. You can secure your database by having front ends access the database with only user accounts with the specific permissions that are required.

[oscara]

Thank you Eli, great work. This content is very valuable; that's why I donate monthly. I encourage others to donate as well.

[kostyashoomsky]

I've just finished watching your Linux series and OMG, they're so helpful! Now I'm gonna watch all the MySQL videos here. Thank you very much Eli for all the content you've provided! This is priceless!!! I'm so happy that one day I stumbled upon your channel and I'm gonna stick to it until I watch and learn everything that's in here!

[francisdiedong]

As always, great content. Let's keep donating to help Eli to give us more of this stuff

[silentlearner]

Amazing explanation,
I love the way you give a bigger picture before diving in. It really helps💯💯💯
Thank you so much Eli

[Shanks_]

(Bob+1)/ Twinkie = What?, the greatest equation of all time.

[pandalanhukuk]

are you doing in the future a video where the content will be operating systems? it would be great to understand how operating systems are connected to the World Wide Web.

[pandalanhukuk]

Docker, Kubernetes were also very interesting topics.

[socoool]

Thanks Eli for the Video,


You are my first IT source of information, I am in a IT Security team and I have a question to you please.


To handle IT Database Security solutions (Oracle & IBM Guardium), what are Database skills you need ?

I never worked with Databases.



Please Eli I really need your advise .





Thanks and regards

[dannysouthern]

Hi, talking about MYSQL database, what about if the databes loading become slow because of lets say 20K categories and lots of values connected to the categories, how would you go about speeding it up, would you have each category tree and its values under its own table.

[warlikelaughter]

8:10 I'm no programmer but that sounds logical right?

[julessaintemartine]

I'd rather learn from Louis Rossmann