Go KonMari on your SQL - Queries with the SQL-Police

Let’s dive into the mess that we get ourselves into when naively relying on JPA and its implementations and see how to generate nothing else but SQL statements that spark joy!
Spring Data, JPA, Hibernate got our backs though to avoid messy database access, right? HELL NO! All they do is teach you a lesson to not rely on other systems without verifying the fundamentals functioning as expected yourself! There is tradeoffs with every framework and you do not want to iron out those kinks in production.
We will look at common anti-patterns that we tend to apply when relying on the JPA-ecosystem and how to regain control over the database layer of your applications again.

Transcript

2. Roadmap 1. What had happened was… 2. Looking under the Hood 3. Batching the Batch 4. Why you tellin’ me this? 4
3. What to expect from this talk? 5 Vlad Mihalcea
4. Do it RIGHT. What had happened was… 01
5. The Tale of the Item Availability 7
6. The Architecture 8
7. Soooooo much Data 9
8. Soooooo much Data 10
9. What any seasoned developer would do… 11 More Pods More Database Connections Check for slow Queries
10. What any seasoned developer would do… 12
11. Do it RIGHT. Looking under the Hood 02
12. DataSourceProxy? 14
13. DataSourceProxy! 15 Query Logging Slow Query Logging Query Count Tracing Method
14. The n+1 Problem 16
15. The n+1 Problem 17
16. Do it RIGHT. Batching the Batch 03
17. Making the Batch batch 19 Align sequence allocationSize with batch size Implementing Persistable for isNew = true @Embeddable for WHERE (field1, field2) IN (?,?)
18. Do it RIGHT. Why you tellin‘ me this? 04
19. Get to know the Tools you inevitably (are doomed to) work with
20. Big Thanks! & ways to stalk me… 22