[Chandler-dev] [Sum] The Great Architecture Discussion of 2007
vajda at osafoundation.org
Tue Oct 9 22:52:27 PDT 2007
On Tue, 9 Oct 2007, Phillip J. Eby wrote:
> And, it is likely that for some period, we will still back-end to the
> repository -- we just would go through a mapping layer of some sort first.
> (And that would mean that we could do some physical schema tuning there,
> without needing to mess with the application layer.)
As was said in earlier quips, Chandler was designed with an infinitely
scalable and infinitely fast repository in mind. It seems to me that the
application layer needs to be "messed with" to no longer work with that
assumption. No amount of relational model is infinitely scalable or fast
either. If the app keeps its current frivolous repository use patterns - the
SideBar collections come to mind - the new model, whatever it is, is not going
to fare well. This includes a "newish" model where we add a mapping layer
between the existing repository and the app layer.
I'm all for adding such mapping layers giving us better nimbleness in tuning
or trying various implementation approaches, but these are not infinitely
scalable nor fast either.
More information about the chandler-dev