[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: scaling object databases
> > I have some ground-level ideas on how to implement master-slave
> > in Ozone; a question would be whether it is sensible to tackle
> that sort of
> > problem at this stage in Ozone development when I need a product in six
> > months. Is Ozone stable enough in a high-traffic environment to make it
> > worthwhile instituting mySQL-style pyramid master-slave
> clusters of Ozone
> > servers (or similar)? I'd rather end up with a better Ozone --
> or other open
> > source ODB of choice in which I get the speed of putting the
> business logic
> > inside the server -- than either a) paying for proprietary code
> that does
> > the job right now, or b) implementing a persistance layer that
> translates to
> > SQL. I'd like to hear thoughts on the realism of such a project from
> > existing developers, however...
> What are the actual qualitive and quantitative requirements of
> the application
> you need this scalable system for? How many users? How many
> objects? What kind
> of transactions? Distribution? Fail-over?
> If ozone is a canditate at all highly depends on those requirements.
Some estimates from the files and prototyped code:
a) 1 million users
b) each user performs 20 transactions/day
c) half of the transactions are read-only
d) total data amounts to 50 million objects
e) average transactions affect 10 objects each, either reading or writing.
f) physically, the overall system is very centralized. If there are
clustered servers, they will all be in racks in the same hosting location.
g) uptime is a priority, so the system must have failover capability.
Comments on the suitability of Ozone?