Geek Answers Handbook

Configure database files and tables

I am particularly interested in a scenario with several servers having daemons that run on specific configuration parameters. (since this is a training exercise, I welcome any thought outside this particular case) The question is where the configuration parameters should be located.

but. central database table

B. configuration file clicked into each of the fields

These are the most common problems that I have encountered. Significant others, in code constants (must be recompiled for deployment. So bad option if they really are not constants), the configuration file is mounted in a common location.

I just wanted to know from the community how you are going to make a choice.

+7
design database-design configuration-files
source share
3 answers

It all depends on the scale of the operation you are managing.

If the number of seats is large and / or changes often occur, use the database.

Otherwise, use configuration files.

If access to the centralized database is too slow or unacceptable, the point of failure, but the scale is still large, use an automated system such as Puppet.

+6
source share

Most companies that need to distribute configuration settings between servers / applications ultimately create their own customization mechanisms and store them in a home relational database. I would say that scale does not matter. Having to log in to multiple servers to verify the file system configuration is a nightmare. However, even when managing configuration in a central database, you still need to make sure that the configuration is easily accessible. I saw this configuration used by three different companies, and the only place where it was used really successful was that the application opened a simple user interface that allows system administrators to configure settings. If it is accessible only using the SQL client, you will find that the configurations will be easily "lost" or worse, duplicated.

The aforementioned poster mentions Puppet, which I have never used, but it looks VERY interesting. However, it does not seem to support Windows yet [1]: http://www.puppetlabs.com/puppet/requirements/

+1
source share

If configuration properties can be updated at run time, centralizing the properties in the database will make life easier.

+1
source share

More articles:


All Articles