There’s nothing wrong with it. Enterprise environments often do it so business rules and logic live in one place, so application code (in multiple languages) do

There’s nothing wrong with it. Enterprise environments often do it so business rules and logic live in one place, so application code (in multiple languages) doesn’t have multiple implementations. I think a few things came together to make programmers crap on stored procedures and putting business logic in the database: - OOP, which typically treats relational databases as dumb backing store for objects. - No enterprise experience, and weak RDBMS/SQL skills. - Popular open source relational databases with weak and clunky languages and tools, such as MySQL. Compared to Oracle and SQL Server the low-end RDBMSs most programmers learn look hobbled. - Unless you use Oracle or SQL Server or DB/2 you may have trouble debugging procedural code running in the database. If this style works for you don’t worry what other programmers say or what you read online. No matter how you choose to build your application you will get people telling you that you made bad choices.