NYCPHP Meetup

[cliff]

Interesting idea, albiet a bit over my head. I like the idea of limiting the
DB as single point of failure. On the other hand, a DB-intensive application
is practically useless in the event of a DB failure anyway.

> First, I'd start by splitting out the global settings (consistent
> across servers) from local settings (local paths, accounts, etc). If
> you develop your application with events/triggers, you could then use
> xml-rpc to update all of your servers from the global settings, and
> keep the local settings separate.
> 
> We've done a similar setup with Joomla 1.5, so you can use xml-rpc 
> and register an update plugin to fire off when that event happens. I 
> try to avoid putting too many config settings in the database, as 
> that really limits your options in the event of a database failure.
> 
> -- Mitch