Skip to content

Configuration Categorization

Matrix

  • Support different dimensions of configuration | | Startup 1 | Resource/ext. service setup 2 | Usage/Tuning 3 | | Global | | | | | --- | --- | --- | --- | | Environment | | | | | --- | --- | --- | --- | | Application | | | | | --- | --- | --- | --- | | Node | | | | | --- | --- | --- | --- |

1 Startup configuration: java options, Environment Variables 2 Setup configuration (addresses, usernames, passwords) 3 Usage /tuning are parameters that change how the application behaves. Performance tuning is a typical example.

Examples to illustrate what kind of configuration goes into each category

  • Global

    • Tweak/usage defaults

  • Environment

    • JMS-server
    • The name of JMS Destinations to use
    • JDBC

  • Application

    • Tweak/usage overrides
    • Resources (e.g. a dbms) only used by this application

  • Node specific

    • Distribute work intervals evenly
    • tweak the application according to OS or hardware specifics (e.g. number threads must match available cpu and memory) While these seems like valid configurations parameters, moving this responsibility to the application should be considered.