I was fortunate enough to be shipped off to Siebel by an employer -
for a 2-week training course on "programming" their CRM.
I was amazed at 1) how a huge corporation could actually develop good
software - with strong architectural oversight in place, and 2) how they
had written the whole database end in true ansi sql - so the thing could
be deployed to any *dbc compliant database platform.
While the nuts and bolts of the course are a distant memory to me now,
those 2 points have stuck with me to this day. Apparently, it is quite
possible to develop a SQL-based application that does not become married
to the platform; but you need to be diligent.
Of course, this was right before Oracle took Siebel over, so no telling
what the situation is now!
I think the sql-less revolution just reinforces the practice of
isolating your DAO's, so you can theoretically just swap out that
'module' when technology and/or client demands it. Moving an app to GAE
is one more example.
Al
On 10/1/2011 2:15 PM, Baz wrote:
(snip) I've almost never worked on an app that wasn't married to its DB.
--
official tag/function reference: http://openbd.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
