Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
- From: frebe73@xxxxxxxxx
- Date: 31 May 2006 09:28:08 -0700
Even when the relational model is a good candidate, the specific vendor
does not need to be chosen up front. The decision to use Oracle or
MySql can be deferred until very late in the implementation process.
Clearly some companies have made committments to one vendor or the
other, in which case the decision is moot; but in that case the
decision is non-technical. In any case the software should be designed
such that the vendor can be replaced without undue hardship, which
means that most of the special features provided by the vendor should
be ingnored, and the software protected from the vendor API by an
abstract interface. (using OO technology.)
I am afraid you are not talking about JDBC/ADO/ODBC as an abstract
interface. Making custom abstract interfaces for every application is a
very clumsy an inefficient way to achieve vendor independence. If you
don't think an interface such as JDBC gives you vendor independence,
use another generic interface on top.
Fredrik Bertilsson
http://frebe.php0h.com
.
- Follow-Ups:
- References:
- Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
- From: bruno at modulix
- Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
- From: Ed Kirwan
- Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
- From: Robert Martin
- Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
- Prev by Date: Re: Template Method vs Strategy
- Next by Date: Head First Design Patterns
- Previous by thread: Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
- Next by thread: Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)
- Index(es):
Relevant Pages
|