Surviving without a database framework
summary
A legacy Oracle Forms system is migrated to Java 8 without an ORM, producing a 48,000-line web app that keeps about 500 tables and 100 packages and runs all DB logic as stored functions. Database calls use a ProcHelper callable JDBC pattern that binds parameters, executes Oracle functions and maps ResultSets to objects; pagination, caching and audit are hand-implemented. Two gated code reviews, daily 10-minute syncs and CI-deployed DB scripts enforce consistency; result is full SQL control and faster perf debugging but heavier SQL skill requirements and slower onboarding.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:04FLC project architecture
- 5:34Database calls without Hibernate
- 8:46Code consistency via reviews
- 10:13Benefits of no frameworks
- 11:39Challenges of manual programming
- 12:45Conclusion
related talks
43mDo You Really Need Hibernate?
55mModernizing Legacy Code - While Not Bringing Down Prod
52mFrom Irrational Configuration System to Functional Data Store
49mDo You Really Need Hibernate?
17mUpgrading business-proven solutions using modern-day technologies
54mDo you really need Hibernate
33mTips and tricks for the Oracle Database developer
54mTesting in Legacy: From Rags to Riches
