title: Xml vs. Database for application configuration
body: <p>My application configuration is very hierarchical and fits nicely into a single XML.
  Soon (YAGNI, Yeh) parts of this information will be consumed by other applications remotely, which calls for a database.</p>
  
  <p>So, I went into designing DB tables and mapping them back to my application's class hierarchy (using EF). however it became a maintenance nightmare.</p>
  
  <p>I'd love to hear from others experience considering this issue, thanks.</p>