>> to write all your business logic in Oracle PLSQL.
I've noticed this (all logic in the db) is common among those developing financial applications. Also .net ms sql server seems to favor it as well. Maybe because they overlap. It's not an inherently bad thing to put business logic in the db; auditing and logging can be simpler, and change control can be more tightly enforced. Be aware that as a developer, it's really common to eschew things not in your code, and check your prejudices. Are they well founded?
I've noticed this (all logic in the db) is common among those developing financial applications. Also .net ms sql server seems to favor it as well. Maybe because they overlap. It's not an inherently bad thing to put business logic in the db; auditing and logging can be simpler, and change control can be more tightly enforced. Be aware that as a developer, it's really common to eschew things not in your code, and check your prejudices. Are they well founded?