Re: Mixing OO and DB

From: Patrick May <pjm_at_spe.com>
Date: Fri, 29 Feb 2008 18:27:15 -0500
Message-ID: <m2od9z1gz0.fsf_at_spe.com>

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.

Regards,

Patrick

---

S P Engineering, Inc. | Large scale, mission-critical, distributed OO

                       | systems design and implementation.
          pjm_at_spe.com  | (C++, Java, Common Lisp, Jini, middleware, SOA)

Received on Sat Mar 01 2008 - 00:27:15 CET