[Cosmo-dev] Deployment of Cosmo persistence load distribution

[Brian Moseley]

On 7/26/06, Jared Rhine <jared at wordzoo.com> wrote:

> Hmmm, I don't think that's true.

you don't think it's true that we don't have a concrete feature list
for 0.5, or for beta? have you guys been doing some planning of which
i'm not aware?

> Double hmmm, I suspect other may have more to say about this.  I know I've
> stood up in a staff meeting and put some dates on Alpha and Beta, and more
> than one PPD posting has dates.

remember that i was on vacation for a month. if there are wiki pages
with this information, i'd love to see some urls.

> + No major architectural layers get added during Beta; all the layers
> necessary to scale to large volumes is in place before Beta.

i'll agree with this only if we have concrete requirements for
performance and number of supported users. scaling is an ongoing
process, and new orders of magnitude often require re-architecture. we
need to set some realistic goals for launch and then plan how to get
to higher numbers after.

> + 2 MySQL database servers

master/slave?

> Let's say we do Hibernate first, and then add a locator service later (which
> takes say a month; I'd advocate doing both in parallel, but hypothetically),

the limiting factor is development resources. our team is not large,
and (i assume) there are more scooby and cosmo features to develop
beyond those concerned with scaling the server to the service's user
goals.

we're absolutely going to have to get started very soon on identifying
the features needed for the production launch and planning how to get
them done.

> Anything that you think can reasonably be done to get load-distribution
> dependencies like database-to-use lookup earlier into Cosmo would really
> help provide some flexibility in the Hosted Service schedule.  I expect the
> most helpful thing to do is standby patiently while the Hibernate code gets
> written and we start regrouping after that.

we can possibly start moving forward on other things in parallel. my
main concern is knowing exactly what needs to be done, and figuring
out the dependencies between items, so we know what to do first.