-1

Actually Im working in a RoR project which must handle more than 10000 requests per day for online data transactions, we have been thinking in mysql but we have doubts about if is enough secure because the sql injections are so popular in this moment (2013), we also think in noSql databases but i found this post:

Is nosql Database good for Online Money Transaction management

it's worring for this part:

I have read in a blog that NoSQL database are not so good for Online Money Transaction i.e. where data integrity is highest importance.( My product has Online money transactions )


Without truly knowing what your product is, it is hard to say whether a NoSQL database would / would not be a good fit. If the primary goal of the product is "Online Money Transaction", then I would suggest against NoSQL database ( at least today in the year of 2011 ). If "Online Money Transaction" is just one of the requirements, but not "the core" of your product, depending on what "the core" is, you can definitely give NoSQL database a try, and for example use an external service to process (e.g. Google Checkout, etc..) your transactions with a guaranteed consistency.

I would like to listen your opinions about which you consider the more appropriate DB for this purpose.

Community
  • 1
  • 1
Jorman Bustos
  • 799
  • 2
  • 6
  • 12
  • SQL injection can be mitigated, ruby on rails has pretty good features to prevent such attacks, and many organisations use MySQL databases without problems, so I don't think it's fair to say that it's not secure enough – Slicedpan Dec 05 '13 at 15:43
  • I honestly think you should do some more research, as SQL Injection is not a "MySql" or even a "SQL" issue.... It's a poor programming issue... Going of your question alone, it would be in your interest to get a firm grasp on these concepts prior to executing whatever it is you are doing. Good luck. – omarvelous Dec 05 '13 at 17:21

1 Answers1

0

It's impossible to say what the best database is. MySQL should work fine for 10K requests per day and can handle transactions and is ACID compliant. Percona is a fork of MySQL that is compatible with it and probably worth looking at. Maybe MariaDB as well.

Possible MySQL alternatives include VoltDB, which is also ACID and RDBMS. If you need to do OLAP, Vertica is a possibility.

Explosion Pills
  • 188,624
  • 52
  • 326
  • 405
  • Depending on your transaction rate Vertica would not be a good option as it dosn't handle well more then 20 transactions(insert,updates,deletes) per second – Up_One Jan 07 '14 at 16:18