Managing Data in Jakarta EE Applications
summary
Shows a concrete repository-based design that isolates data from business logic, using interfaces implemented for JPA and MicroStream, wired by CDI and tested with JUnit/Mockito and Testcontainers. Demonstrates a running app on Open Liberty with Docker-backed Postgres, CRUD implemented in abstract base repositories, and Jakarta Data features (insert/update/delete annotations, lifecycle hooks) already usable in beta. Includes working demos: counting users, creating and fetching records. repository interfaces with CDI injection MicroStream and JPA implementations Jakarta Data beta on Open Liberty
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 2:09Early Java EE data handling challenges
- 7:13Shift to enterprise frameworks
- 10:52Isolating data layer with annotations
- 13:09Repository pattern explained
- 17:28Domain objects and repository structure
- 24:40CDI integration and boilerplate reduction
- 27:55Future with Jakarta Data
- 31:52Live demo setup
- 36:03Custom repository implementation demo
- 40:48MicroStream repository demo
- 44:15Q&A and closing
related talks
49mUnlocking Data Access Excellence with Jakarta Data
50mJakarta Data and Jakarta Persistence
48mA Developer's Guide to #JakartaEE 11
26mUnlocking Data Access Excellence with Jakarta Data
45mJakarta Data - Standardized Data Access for SQL and NoSQL Databases
34mSimplifying Polyglot Persistence Integration with...
01h 00mApplied Domain-Driven Design Blue Prints for Java EE
50mJakarta Data and Jakarta Persistence