Re: Mixing OO and DB
From: Eric <eric_at_deptj.demon.co.uk>
Date: Sat, 1 Mar 2008 11:02:21 +0000
Message-ID: <slrnfsidtt.do7.eric_at_tasso.deptj.demon.co.uk>
>>> frebe <frebe73_at_gmail.com> writes:
>>>>> Typically, once a core set of objects have been instantiated,
>>>>> access to related objects is via reference rather than repeated,
>>>>> explicit database access.
>>>>
>>>> And obviously introducing synchronization issues...
>>>
>>> You are assuming that the database is always the system of
>>> record and that the system is data-centric. Those assumptions are
>>> not always valid so your "obvious" synchronization issues do not
>>> occur. There are more ways of building large scale distributed
>>> systems than are dreamt of in your RDBMS.
Date: Sat, 1 Mar 2008 11:02:21 +0000
Message-ID: <slrnfsidtt.do7.eric_at_tasso.deptj.demon.co.uk>
On 2008-02-29, Patrick May <pjm_at_spe.com> wrote:
> Eric <eric_at_deptj.demon.co.uk> writes: >> On 2008-02-29, Patrick May <pjm_at_spe.com> wrote:
>>> frebe <frebe73_at_gmail.com> writes:
>>>>> Typically, once a core set of objects have been instantiated,
>>>>> access to related objects is via reference rather than repeated,
>>>>> explicit database access.
>>>>
>>>> And obviously introducing synchronization issues...
>>>
>>> You are assuming that the database is always the system of
>>> record and that the system is data-centric. Those assumptions are
>>> not always valid so your "obvious" synchronization issues do not
>>> occur. There are more ways of building large scale distributed
>>> systems than are dreamt of in your RDBMS.
>> >> So what is the system of record? > > For some systems I've worked on recently, it has been a highly > distributed shared memory holding a disjoint object graph. >
With no persistence or backup? Received on Sat Mar 01 2008 - 12:02:21 CET