I Welcome back to Module seven. Course closing. This is Lesson one course review
and we're in the last sub lesson 1.3. Where to go from here.
So we made it to the last module lesson in the course. I really hope you enjoyed it. I really hope you learned some sequel along the way.
Now, where do we go from here, though? Well,
the best thing to Dio and the old saying practice makes perfect really applies here. You definitely want a circle back and practice some of those concepts that you either had difficulty understanding or difficulty implementing. And also, if you notice some other areas within those concepts that you want to explore, most definitely do that explore the
take a deeper look at concurrency operations and how
to effectively control multiple users acting
accessing the same resource at the same time.
After that, after you've practiced sequel and got a really good grasp of it. And you're you're a master of the relationships, your master, that joins your master of the foreign key constraints and you can really develop a really good looking schema. The next thing you want to do is you want to get good at
best practice and standards and learn a design pattern or two. Now there's multiple reasons to do that, one of those being that it'll help in job interviews as you'll know the best answer when posed a the best way to solve a certain problem.
The next reason is those best. Those standards and design powder served a really important purpose, and that is to generate a code based that is easier to maintain. That is easy to implement features in now
that becomes much more important as an application grows in size.
If you have a small application like our CMS data base, which could correctly track articles, comments and user's data, but it really wasn't that complicated. If you did follow the standards in that application, it wouldn't be a huge deal, because you it's not a very big application, so you can quickly
follow the code that does exist in it around.
Now where it becomes a big deal is when the application grows in size, like the axiomatic a database has,
Um, in any case, you can have production database where you have thousands of tables. And if you have followed those standards, it'll make reading those that database in those tables much more easier. And you don't have to do any of that guessing. For example, in ah, the acrobatic A database you might see two tables where you have that the account.
Ah, I D. On one and employee number on another now is to be account i d. The employee number. Are those equal? Maybe they could be. There's only one way to really to find out if the floor and key constraints stop there, and that is to just connect them via that entry point and see if the data makes sense that you're looking at. And that's not always the best way to do things that much.
It's much better to see that relationship there and just know that you have the right answer.
So that brings this course and lesson to a close. I hope you enjoyed it. I hope you got to learn a lot about sequel, and I really hope to see you in a future course. Thanks for your time. By