We’re evaluating EE for our primary site and have a couple of questions:

1.  We have multiple production web servers, and need to have a setup where one EE installation (not one of the production web servers) will be used in the backoffice by our content creators.  This data will be periodically pushed to the production servers, with their own MySql instances.  For security reasons, it we would like the MySql logins used by the production servers to have read-only access to the database.  Trying this fails, however (lots of writes to the database).  Is there any way to configure EE such that it doesn’t need to make these writes?

2.  We must review all content on our site, including user comments, before it is published.  Is there some way to make the database reads/writes asymmetric, so that reads are done from the production database, but writes (like user comments) go to a separate database, to be reviewed and published later?

Any help is greatly appreciated, thanks in advance.

Moderator’s note: Moved to Pre-Sales.

Hi UncleFunks,

1. Nope. The idea behind EE is that you can write content to a database which requires EE to be able to write to the database. As for security, you can restrict what a person has access to in the Control Panel so that there is no chance of a person with Control Panel access compromising your database.

2. No way to do this either as EE uses a single database. However, you can certainly moderate comments before they go live on the site. You can set this on a per-weblog basis.

That answers my questions, thanks.  I appreciate the quick response.