Java Beyond Frameworks: Avoiding Lock-In with Agnostic Design
summary
Shows a concrete migration path: replace Spring annotations with JSR‑330 annotations, move domain logic into a framework‑free module, and keep Spring or Quarkus confined to a deployment module so core code never changes. Demonstrates database access with Jakarta Persistence (JPA) plus Hibernate as an implementation, cloud secrets fetched via direct HTTP using the Jakarta REST client instead of vendor SDKs (Azure Key Vault example), and a successful swap from Spring Boot to Quarkus with zero changes to core—tradeoffs: more custom code, tests and documentation.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 3:21Architecture design principles
- 7:25Replacing framework annotations
- 10:40Isolating business logic
- 14:52Cloud API abstraction
- 22:02Database abstraction
- 28:01Framework switching challenge
- 35:15Trade-offs and conclusion
related talks
01h 00mFantastic Frameworks and How to Avoid Them
31mMigrate to Quarkus, this is the way
25mQuarkus Hands-on Workshop for Spring Developers
54mEnterprise Framework Battle: Quarkus vs. Spring Boot
01h 22mModern Java Component Design with Spring Framework 4.2
42mMigration to Quarkus
41mMigrating an Application from Jakarta EE to Quarkus
44mKeep Spring at Arm's Length!