About this course
When analyzing Laravel project performance, I often see that the underlying problem reasons are poor database structure decisions.
So, it's beneficial to plan your DB structure in a way that would stand out the test of many more records in the future, but also be flexible enough.
In this course, we will cover questions, like:
- What relationship to choose?
- Is it worth saving data in UUID/JSON/Enum columns?
- Practical cases of structuring DB invoice numbers, e-shop attributes and more
The lessons will contain a lot of practical examples, with links to Migration files from real open-source Laravel projects.
So, let's get into it? We start with the first most important lesson about relationship choice.