Have you ever used JPA Entity Graph in your last project to optimize queries?

Yes, in the last project I used JPA Entity Graph to optimize queries and prevent the "N+1 select" problem.

Entity Graph allows explicitly specifying which related entities should be loaded together with the main entity, helping to control eager or lazy loading.

Example of usage:

@EntityGraph(attributePaths = {"orders", "profile"})
Optional<User> findById(Long id);

This allows loading the user along with their orders and profile in a single query, reducing the number of database accesses.

Using Entity Graph improves performance by reducing the number of SQL queries and retrieving data more efficiently.