Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Around 10 years ago, a work collegue improved the ETL processing time of a Java application from minutes to a couple of seconds, by dropping hibernate and using direct JDBC instead.

If all one is doing is calling createNativeQuery() all the time, and having stored procedures as well, then it is just needless fat.



If you have a trivial app that just executes a couple queries, then sure use JDBC?

I do not understand your point. Most business apps are not trivial.


Who said anything about it being a trivial app?

It was an ETL stack for distributed networking monitoring, and data reporting.


If you can comfortably use JDBC for data access, then your data access logic isn't very complicated. There's nothing wrong with that; use the right tool for the job.


I believe the exact opposite


Who said it wasn't complicated?

Using SQL with JDBC isn't a synonym for bare bones string concatenation.

Offload complex queries to external files, or better yet, stored procedures.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: