From the @QuarkusTest classloading rewrite to lightweight CDI component tests and smarter test resources, here’s what modern Java developers need to know about testing in Quarkus
However, I notice in most of your articles that use JPA/Panache you tend to mix both the Panache Active Record Pattern AND the repository pattern, where you let your entities extend PanacheEntity and then also use a repository to do database actions on that entity as well.
This is NOT RECOMMENDED and can also cause a lot of confusion for new users who are just using your code as reference. You should be picking one OR the other pattern.
Other than that, I really do enjoy the Quarkus topics you publish and have found them to be useful even as an experienced Quarkus developer myself.
I like your articles and thanks for writing them.
However, I notice in most of your articles that use JPA/Panache you tend to mix both the Panache Active Record Pattern AND the repository pattern, where you let your entities extend PanacheEntity and then also use a repository to do database actions on that entity as well.
This is NOT RECOMMENDED and can also cause a lot of confusion for new users who are just using your code as reference. You should be picking one OR the other pattern.
Other than that, I really do enjoy the Quarkus topics you publish and have found them to be useful even as an experienced Quarkus developer myself.
Thanks, Tim!
You’re right. I want to show too much sometimes. I’ll make sure this is being used more deliberately!
Thanks for the feedback!
M