Comment Re:There are very few cases for stored procedures (Score 1) 266
I ignored the case you mentioned and I should have stated it.
However, if an app is now moving web based and the user base grows exponentially a stored-procedure based system will not be able to scale to handle the growth.
Something else I didn't mention (out of lots of other reasons) is that a corporation wishing to reuse its business logic should not be placing its business logic in stored procedures which can't be scaled and can be very hard to maintain if you use more than one database vendor.
Web Services are a great solution and in most cases should be used instead of stored procedures because web services use http (everything supports this), and have bindings for most languages.
Note that Linux web services using Tux are several times faster than JDBC/ODBC/Java RMI/CORBA and even quite a bit faster (and less CPU intensive) than rolling your own sockets based protocol.
However, if an app is now moving web based and the user base grows exponentially a stored-procedure based system will not be able to scale to handle the growth.
Something else I didn't mention (out of lots of other reasons) is that a corporation wishing to reuse its business logic should not be placing its business logic in stored procedures which can't be scaled and can be very hard to maintain if you use more than one database vendor.
Web Services are a great solution and in most cases should be used instead of stored procedures because web services use http (everything supports this), and have bindings for most languages.
Note that Linux web services using Tux are several times faster than JDBC/ODBC/Java RMI/CORBA and even quite a bit faster (and less CPU intensive) than rolling your own sockets based protocol.
