‫What's going on, guys?
‫My name is Hussein, and this course is one of the causes that I am really, really proud of building
‫and introduction to database engineering.
‫This part, of course, is is a course that I wish I had 15 years ago, and that's how I actually built
‫it.
‫I built this course in a way.
‫It's like, OK, if I am new, if I'm just starting out my career or I have I know a thing or two about
‫databases.
‫I know school and very basic things.
‫I studied in the uni university in college and I want to know like what is out there, what is people
‫doing in the professional world.
‫I wish I had a course or a book that kind of touched upon this concept.
‫And that's exactly what I did.
‫So I built this course not as a practical Hands-On.
‫Kind of boring, dull cause that you have to follow, right?
‫It is it tastes different sectors and database engineering.
‫And and I believe these are.
‫Seven or six parts of database engineering that anyone who wants to dive deep into database engineering
‫should know.
‫Now, what are you going to learn in these scores?
‫You're going to learn the basics of databases like anything that database engineers should know.
‫You will not like what is acid right?
‫At the consistency in isolation and durability, very detailed tests are going to show some examples,
‫obviously.
‫And then you're going to learn about index.
‫You going learn about concurrency control on databases.
‫You're going to learn about partitioning.
‫You're going to learn about sharding.
‫You're going to learn about deep indexing ideas as well.
‫And I go into a little bit of touch about advanced and I go through how do you actually apply these
‫concepts in real wars.
‫So I will actually do a system, a database system design with you guys and just walk you through exactly
‫how I think through things and then design a database system for a given problem.
‫So that that is very interesting.
‫Right, because you now put your the skills that you learn into use into the SCHAUS essentially.
‫I will also discuss database engines, the concept of database engines and how does it differ from a
‫database system.
‫Right.
‫And how is this really critical to think about when you actually design an app that consumes the nature
‫of the app actually matter?
‫Because that will.
‫Infer your decision to pick a database over another.
‫I go through that whole bit as well, so that is really, really interesting stuff to me, especially.
‫Right.
‫And the final part, I have a special section with Global for Advanced Topics to discussion that just
‫thinks that.
‫I think that just open discussions, whether we should use quick databases or not or quick the protocol,
‫whether whether we should how how how often should you implement your own Blum filter versus relying
‫on the one that is on the database and things like, I think the very things that just pick your curiosity.
‫So, guys, if you decided to go this course, I really appreciate it.
‫And what are you going to learn?
‫Is, is the ability not you're not going to learn at Postgres or my school?
‫I have to be honest with you, because these are very easy to pick up.
‫You're going to learn the system.
‫You're going to learn the abstractions and the fundamentals essentially and first principles.
‫And then I think once you're finished with this course, you will start asking your own questions.
‫OK, I have this application or this back in the application.
‫And in order to build it, oh, I need this kind of database.
‫I need this concept.
‫Concept.
‫Oh, I need indexing.
‫I need partitioning.
‫I don't think I need Qadeem because it's a little bit of overkill.
‫You'll start automatically asking these questions because they will come to your radar essentially.
‫And the way I explain things and you know me from my YouTube channel, it's always like I try to ask
‫the same thing to myself, like, how do I start with these things?
‫Like there's so much out there.
‫So I lay them down into a progressive manner.
‫It's like, OK, so this learning none of those entities.
‫And when I say learn, you don't have to be expert and just look.
‫No, why does it exist?
‫I always ask this question in every every video that I make.
‫Why does a technology exist?
‫And I try my best to answer these questions and the entire nine sections in this course, around six
‫hours, I believe.
‫Yeah.
‫Six hours or I think a little bit more than that.
‫So there's a lot of content.
‫So take your time.
‫Take your pace.
‫This is not something you want to finish and and get over with.
‫This is something just like a dictionary or.
‫Right.
‫Or something you want to go back to and oh this is oh this is what I learned about this.
‫Oh this line a lot about this.
‫So it can jump freely through sections.
‫Right.
‫The course is if I had to apologize.
‫This causes Lobert for intermediate to advanced students.
‫If you don't know anything about databases, I think you're going to be a little bit lost, but.
‫If you know a little bit about what a database is, how to do a sequel, because I don't explain a sequel
‫because there are many, many other causes way better than I do explain it.
‫Many of these courses.
‫Right.
‫Sequel and stuff like that.
‫So I don't teach you like these practical skills to teach you how to apply to your thinking and design
‫your systems to to to the creatives, essentially the creative of system design and how to apply these
‫things.
‫So, yeah, so it's going to be an intermediate to advance.
‫So just pay that in mind when you start this course.
‫And I hope we really enjoy it.
‫I'm going to see the next one.
‫Thank you so much, guys.