3 ms·
When doing consulting for an agency, I was managing the integration of a new iPhone app with a legacy government database. We were given access to their code a
by schappim 10y ago
When doing consulting for an agency, I was managing the integration of a new iPhone app with a legacy government database.
We were given access to their code and their database.
One of my wise old developers frowned and when I asked why he told me there were literally hundreds of stored procedures in this database and no documentation.
It was at this time he told me to when possible keep business logic in code so it can be managed by a version control, and easily replicated for CI.
He advised the exception to this rule was when the stored procedure gave a large performance boost.
- ruslan_talpa 10y agoA few problems with your reply (but thank you for feedback) It's gov, not finance. The fact that there were hundreds and not documented does not mean it wasn't the right place for them to be implemented, can you say for sure that those hundreds of RPC (probably 10 lines each) would not turn into thousands of functions in the code (that can also be undocumented)
- ruslan_talpa 10y agoMaybe the number of functions would not increase much (if you ignore the ORM/framework) but their size i think would suffer because of all the additional code for turning rows to objects.