Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 2
    How do you define what is configuration and what is data though? Commented Oct 26, 2016 at 3:22
  • 6
    Your answer doesn't explain why storing a configuration in a database violates separation of concerns (the concern of a database is to store data; it doesn't care what data you store there), or why this is a bad thing, and your answer is now being cited elsewhere as proof that it's a bad thing. Commented Aug 25, 2017 at 14:59
  • 1
    databases can change on demand. we can have them being asynchronous like mysql. Does static files support this? HELL NO! So I downvote :) Commented Sep 19, 2017 at 9:15
  • 1
    @AmirHossein Static files support change on demand as long as they're not locked. That's no argument. Commented Jul 9, 2019 at 18:13
  • @AmirHossein +1 to the notion your argument is flawed. The conclusion you reach is convincing only if you ignore (possibly more common) use cases. If you feel the config needs to be "asynchronous" then (if I understand what you meant by that) then you can pull the config files from a Object Storage microservice. As you say, databases "change on demand" which in my experiences has ALSO meant "our service is down because of the database folks". IMO a good reason to use a database for configs is when you require relatable config fields, and even then try not to poll the db directly. Commented Mar 4, 2021 at 13:10