Just stumbled onto some excellent papers regarding architectural considerations in today's jumble of technologies. Interesting to see the reference to APEX - Oracle HTML DB in the Thick Database paper. Great that Paul added the examples of relative efforts/time/lines of code there! Nice work.
Dulcian Papers - Thick Database
One thing I'd be keen to see is APEX vs. Thick Database application examples in terms of effort... okay I hear the "but APEX ain't following the guidelines". Nevertheless if a technology works for you, use it!
Also I threw together a table with additional "minutes per line of code" columns just for fun ;-)
| Mins per line of code Database | Mins per line of code Java | ||
| Case 1 | Conventional development | n/a | 1.44 |
| Case 1 | Thick database development | 4.80 | 0.80 |
| Case 2 | Conventional development | 2.40 | 3.60 |
| Case 2 | Thick database development | 3.60 | 3.60 |
| Case 3 | Conventional development | 2.09 | 4.43 |
| Case 3 | Thick database development | 1.23 | 3.43 |
Any opinions appreciated.
2 comments:
Certainly like the idea of getting as much intelligence as possible into the database (unlike Oracle Apps' forms), although I probably wouldn't push it as far as article suggests by preference.
By the way, the article link is busted - use link instead
Hi Tony,
Thanks, fixed the link.
Gareth
Post a Comment