There are two reasons why I'm not using a database (a database was my initial thought as well). Firstly, reliabilty is crucial. The system does write data to a database, but should that database be down, it has other (multiple) mechanisms so that no data is lost. I could possibly do something similar on the config side (ie. have a failover config file, but normally read out of the database), and that might not be a bad option, but I'm wondering if there are any others.
The other reason is mainly political - the current application doesn't use a database for it's config (although it's woefully inefficient), but it's realiable (ie. there's no DB server to go down). Reliability is above efficiency in this project..
The ideal would be to have some sort of High Availability Db server in place, but that infrastructure doesn't currently exist. Hopefully, I can do this in the future, but currently my hands are tied.
In reply to Re^4: Configuration Files
by Mutant
in thread Configuration Files
by Mutant
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |