When it comes to finance, SQL comes out on top - things like MySQL have been battle tested for decades, accounts information is intrinsicly relational so relational databases are the right fit, ACID compliance with nosql is more liberal but with your project you'd need 100% reliability.
Also theres transactions and atomic operations, which strictly couple two entries to ensure that if you debit one place, you credit another place. NoSQL doesn't have the same level of capabilities. If you'd asked for something super fast, pleasant and exciting to use, its nosql all the way. But for finance, SQL. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
