I have several global variables that I need to store in a database. These variables rarely change, but when they do, all installed instances of the application must updated to those changes, which is why I think the central database is the appropriate place for them.
The variables are not linked to any "concept" in the database and are not related to one another. They are just standalone values. An example is "the address of an external API". Another one is "the default download bandwidth value".
I have seen in some StackOverflow posts, that in such cases it is recommended to create a "single row table" in the database, with a column for each variable. But I don't have a good feeling about this. It feels like I'm hijacking the concept of "database table" to store my values in a single row.
Another suggestion was to create a "key-value" table, where the key is a string representation of my variable. For example, "API_ADDRESS". But this requires me to create additional structure in my backend in order to map these key to meaningful concepts. And I am under the impression this can quickly become cumbersome to manage.
What is a good way to do what I'm trying? Is there a standard solution?