Question

I am a newbie in Hibernate.

I am working on a cloud service data access layer.

Currently we are using Hibernate for OR mapping and as data access layer using Hibernate annotations. But lately i have been asked to implement Hibernate/Data Access layer in such a way that my stored procedures be in HQL and we can change our DB at a short notice and port our entire code.

The closest i can think in this regard is by using Named queries , where stored procedures are at DB side and my hibernate is resolving the stored procedure calls using named queries.

The reason for all that is the notion that since stored procedures are precompiled therefore they give good performance and security optimization for a large cloud service implementation.

currently i am using java , hibernate and Mysql.

Can anybody examine my assumptions and validate or give/suggest some better alternatives.

Performance and security are top priority.

Answer 1

I think the approach you outlined is great.

That is exactly what I would do if I were in your position. (I’m on Hibernate backed by MySql also, and have considered doing this if needed for performance reasons.)