Re: [Clockwork-developers] Architecture of job scheduler

[Shawn M. <smc...@ei...>]

This one time, at band camp, Charles Brian Hill wrote:
>=20
> If we go centralized, I think we might as well pick a full-fledged SQL
> database platform (hopefully a free one) and standardize on that.  A
> centralized system means we're dependent on a single server, and if that's
> the case, that server is liable to be very, very busy.  If we wanted to h=
ave

If we do that, we want to take advantage of ALL the features of a real
database, so we shouldn't pick a MySQL type of program that's fast but
doesn't care about data integrity; we'd look at more of a PostgreSQL,
where it doesn't wring the last bit of possible speed out, but it
assumes your data is precious.

I think we have to do a free one if we do one at all, because we're a
free project.  We're cutting our own throats if the scheduler is free
but you have to pay Oracle $100k if you want to use it.  I agree that we
can't support every database, at least not in the beginning.