Hi!

Does it make sense to use stored procedures in a new project, that uses hibernate, Spring and PostgreSQL?

Do stored procedures add something valuable or is in most cases basic Hibernate enough?
It seems like going behind Hibernates back.

Are the any good practices or patterns?

As said, the project is from scratch, so there are no preexisting stored procedures or even tables.
Regards,
David

You will likely get some mix answers until you try it your own. But in general I would recommend NOT to use store procedure unless you have no choice. Store procedure is hard to debug and maintain, and it's not a OO language (Java). Not to mention that Stored Proc is highly NOT portable! The number one big benefit of store procedure is that it should* off load your processing power to the DB instead on your application server. Also placing computing logic right on a DB, which closest to the data is typically faster, verse you pull them out into your Hibernate and process them then save them back into the DB. But again same reason you typically don't write assembly code instead using Java on a high level application. Study your requirement carefully, and I would use store procedure only as needed.

Stored Procedure is very useful for the project. It is a subroutine available to applications accessing a relational database system. The major difference is that UDFs can be used like any other expression within SQL statements, whereas stored procedures must be invoked using the CALL statement.