This course is prepared for Intermediate Learners.
What you will learn!
You can learn Querydsl from the basics to practical use all at once.
You can learn practical application know-how beyond simple functional explanations.
JPA can solve dynamic queries and complex query problems.
Say goodbye to complex and dynamic queries! Solidify your Java backend skills with Querydsl.
🚩 This course is a roadmap course.
This lecture is the last lecture to complete the practical course of Java backend development. Please check the Spring Boot and JPA practical complete conquest roadmap first. (Link)
Kim Young-han's Real-life! Querydsl
The latest Java backends mainly use a combination of Spring Boot, JPA, and Spring Data JPA. However, the limitation that this combination cannot solve is the problem of complex queries and dynamic queries .
In practice, we usually deal with complex queries, and in addition, we often use dynamic queries. Depending on the business domain, writing queries can be more than half of the development work. Querydsl is the technology that neatly solves these problems.
If you want to go beyond the limits, JPA + Querydsl is not optional, it is mandatory .
Querydsl helps you to write queries as real Java code, not as text, by overcoming the limitations of the Java language. It not only neatly solves the dynamic query problem that many developers have been struggling with, but also catches all syntax errors at compile time. Although it is written in Java code, it is easy to learn because the syntax is almost the same as SQL and JPQL, and it is also easy to write complex queries.
On top of Spring Boot and JPA, adding two fantastic frameworks, Spring Data JPA and Querydsl, makes development really enjoyable. The development codes that were considered simple and repetitive until now are significantly reduced. Developers can focus on developing core business logic. And thanks to Querydsl, even writing queries can be done in Java code, which is fun. In complex practices, the combination of Spring Data JPA and Querydsl is not an option, but a must.
In this lecture, we will teach you everything about Querydsl , from the absolute basics of Querydsl to the know-how accumulated through various practical projects .
👨💻 Please note before taking the class!
This lecture covers the JPA (JPQL) module of Querydsl .
Learning Contents
I recommend this to these people 💻
Introducing Querydsl
Project setup - project creation, configuration and validation, Spring Boot configuration, etc.
Example domain model
Basic Grammar
Intermediate Grammar
Practical Applications - Pure JPA and Querydsl
Practical Use - Spring Data JPA and Querydsl
Querydsl functionality provided by Spring Data JPA
The book is for those who want to study more in depth. You can think of it as a reference book. (If you do not have a book, separate materials for the lecture will be provided.)
Recommended for these people!
Who is this course right for?
Anyone who wants to solve complex queries using JPA
Anyone who is working on a practical project using a combination of Spring and JPA
[Spring Complete Conquest] Roadmap, [Spring Boot and JPA] Roadmap, I've done them all.
Sigh~~~ I don't want to see Younghan again on Inflearn (it was so hard ㅠㅠㅠ)
I've never left a course review, but I'll leave one word for the first and last time.
[When it comes to Spring, don't be stingy with your money, and take Younghan's lecture.]
(Younghan was a creep to me)
I needed to learn Querydsl in a short period of time to apply dynamic queries, and it was very helpful that you explained in detail how to use it in practice with clear explanations. Now all that's left is to apply it. Thank you! :)
In fact, pure JPA was fun, but after learning about DataJPA, I felt, “Wow, it’s so convenient...”. I’m experiencing this once again. It’s truly the flower of JPA.
I was struck by Younghan’s words that development would become so much fun if you knew about Querydsl. While listening to the previous lecture, I wondered how good Querydsl was that he recommended it so much.
One thing that has changed noticeably is that my fingers are increasingly idle.
While writing a query by opening parentheses and double quotation marks with em.createQuery,
I used to write queries directly with @Query when they were a bit complicated and long, but now I just type s, f, w, f and IntelliJ does it all;; I think my fingers are becoming more and more lazy.
This is why Younghan often talked about Querydsl in the previous lectures! ㅎㅎㅎ
But at the end of the lecture, the saying, 'There is no free lunch in the world' came to mind.
I felt that both DataJPA and Querydsl should be used based on an understanding of pure JPA. If you look at the internal code, it is ultimately an abstraction of pure JPA. Anything convenient has a price. I should go review the basics again to use it better ㅎㅎ
JPA's father, Younghan. He is really the best!
I recommend this lecture!
Finally, I finished the JPA roadmap with this lecture.
Personally,
I had moved from Java backend development to Python backend development,
and I wanted to go back to Java,
so I had to study the changed Spring development environment again,
and I was wondering how to study, and I found Younghan's lecture on Infraon, and that's how I ended up here.
I had a gut feeling that the sample lecture content was extraordinary(?), so I ended up watching all the lectures(?) and I'm really satisfied. It was also a good opportunity to decide the direction of my development studies that I had been wandering around.
Thank you.
I sincerely congratulate you on completing the roadmap. Just the fact that you have made it this far shows that you are a perfect fit for the Java backend developer. I am sure that if you continue to study in the direction you have chosen, you will become a better developer. If you have any questions while studying, please feel free to ask me anytime^^! I will always cheer you on!