I need a small amount of static data in a script that is called about 200 times per day max (spread through an eight hour period). The static data will only change very infrequently (about once a month at first and probably never after 6 months). I suppose I should put it in a config file read by the script but this seems a lot of effort for little gain - particularly as it would need error handling, content validation, defaults etc. It would be much easier to qw/ / it into a list and take the small hit of having to redistribute the code just to implement a config change.
The code is only ever going to live on two servers and they will always have identical versions of the config data. As soon as I needed multiple versions of the config data I would move to a file solution - but in this case it will never (!) happen.
Does anyone have any useful guidelines/rules that they follow for situations like this?