title: Is a document/NoSQL database a good candidate for storing a balance sheet?
body: <p>If I were to create a basic personal accounting system (because I'm like that - it's a hobby project about a domain I'm familiar enough with to avoid getting bogged-down in requirements), would a NoSQL/document database like RavenDB be a good candidate for storing the accounts and more importantly, transactions against those accounts? How do I choose which entity is the "document"?</p>
  
  <p>I suspect this is one of those cases were actually a SQL database <em>is</em> the right fit and trying to go NoSQL is the mistake, but then when I think of what little I know of CQRS and event sourcing, I wonder if the entity/document is actually the <em>Account</em>, and the transactions are <em>Events</em> stored against it, and that when these "events" occur, maybe my application also then writes out to a easily queryable read store like a SQL database.</p>
  
  <p>Many thanks in advance.</p>