Java & Programing languagesConference50min
Java Beyond Frameworks: Avoiding Lock-In with Agnostic Design
This talk presents a layered Java architecture that isolates framework dependencies, keeping core logic pure with Java and Jakarta EE. It shows how to reduce lock-in, decouple business code, and integrate with cloud services while preserving portability, testability, and long-term maintainability across frameworks.
talk.summaryAiDisclaimer
Rijo SamABN AMRO Bank
The Problem: Modern Java apps often get stuck in their frameworks. Tools like Spring Boot and Quarkus speed things up, but they come with hidden costs such as vendor lock-in, heavy dependencies, and rigid architecture. So what happens when your app outgrows the framework or something better comes along?
The Solution: This talk introduces a layered approach to Java development, isolating framework dependencies while keeping core logic pure with Java and Jakarta EE.
Through examples, you’ll see:
Trade-Offs: Yes, this demands more upfront effort, including writing custom persistence layers, rigorous tests, and meticulous documentation. But the payoff is code that’s adaptable, testable, and maintainable across frameworks, teams, and decades.
Key Takeaways:
The Solution: This talk introduces a layered approach to Java development, isolating framework dependencies while keeping core logic pure with Java and Jakarta EE.
Through examples, you’ll see:
- Strategies for replacing framework-specific annotations
- Techniques to decouple business logic from frameworks
- Approaches to cloud integration without framework coupling
Trade-Offs: Yes, this demands more upfront effort, including writing custom persistence layers, rigorous tests, and meticulous documentation. But the payoff is code that’s adaptable, testable, and maintainable across frameworks, teams, and decades.
Key Takeaways:
- Practical patterns for agnostic design
- When (and when not) to adopt this approach