0

My company currently has consultants developing a Java-based application. They are using Hibernate ORM 3.5 (released 5 1/2 years ago in 2010) in this application. The back-end is SQL Server 2012. Should my company be concerned that they are using such an old version of Hibernate? Browsing the Hibernate change logs, I see various performance fixes over the years, but I don't know how much of a difference these make, and if it's worth putting pressure on the vendor to update to a newer version. As a production DBA, my main concern is performance. What do you think?

  • 4
    I don't know that newer versions are all that much better. They're still ORMs, they're still going to try to do 80/20, and you'll still take all the up-front dev time you saved, and spend it in post-release tuning and troubleshooting. IMHO. – Aaron Bertrand Nov 6 '15 at 18:17
0

There could be several reason they continue to use an older version. It may be they've run into issues with newer versions and know to stay away from them. It could also be that they know the version they're on and can be much more efficient working in it which translates in to dollars.

I see later versions lost support for sharding and had an overhaul to services management. These may be features they lost that they like to use.

I would ask them to explain their reasoning for using the older version and then decide on what to do.

This question might get better answers on Stack Overflow since ORMs are used by software developers more than DBAs.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.