@odrotbohm
A great talk, as always! 👏 It's interesting that you casually refer to the proper solution to the problems of the middle part but don't emphasize on it: none of the problems induced by using full aggregate references in the BankTransfer object occur if you model them as identifier references instead. A many-to-… relation simply has no place in an aggregate model. You can avoid the additional mapping customizations, the usage of JPA-specific repository API and query customizations on the repository methods. Most of the JPA query performance issues can – and should – be solved by using less JPA, not more. 😉 Big thumbs up for the recommendation to use projections and the awareness about the pitfalls regarding transactions. 👍
@unus55
Thanks very much. Addressed some of the problems I faced recently
@umanajohan
Esta charla vale oro!!
@PietervandenHombergh
one should consider to do the whole transaction in the database, i.e transfer from and to accounts in the database. that makes up one query to a custom database function, using the connection just once and which also takes care of the transaction.
@sumanthanumula8048
Wow...! Thanks I learnt something new today.
@haroldpepete
Realy helpful talk, a lot of great tips
@tahahajivand1843
so helpful. thanks for your hard works!
@thiagonunes3619
Nice. Tks for share!!
@serengetysson3159
What a great explannation
@gregyeo110
I know this is very practical and nice solution but just keep in mind that we should also keep running the application at least 5 years after development. If the system becomes bigger and bigger, many quires are wasted without performance checking because the production DB is fast enough with them. DB price is cheaper then refactoring or revieweing generally. So please do not over use projection class unless the business logic(use case) requires high performance like batch job. Management of type and design cost keeps increasing and it sometimes causes replacement of application at the end. But N+1 problem is easy to become big issue in production, so the techniques are brilliant and it was nice guide. Thank you.
@dmitry48041
What is the speaker's IntelliJ IDEA color theme?
@circuitbreaker8314
23:10 , you could start a new thread?
@sagarrout007
Thanks, Quality Stuff. One concern or confusion , Whenever we use REQUIRES_NEW, it creates separate new transaction and not nested transaction. Although one starting in another but they are not nested, to be precise, right ?
@kam1234554321