java - JPA vs JDBC vs NoSQL for MMORPG -

We are developing a 2D MMORPG space shooter using Libgdx / Netty and we had to face a question Which we can not solve concerning the data.

• If we use JPA and RDBMS, we can get ACID and reduce the data management code
• If we use the JDBC width of spring If we use support then we can take advantage of the speed but complexity data management code
• We have no experience in NoSQL development, but speed advantage (which is important) Should be omitted

  In our help to fix please.

  1. You realize, that JPA uses JDBC.
  2. Spring can achieve ACID as easily as JPA can not do. I do not know what speed are you taking advantage of the speed of development? Transaction speed? Why Spring Data Management Code Is Complex? This is another false statement.
  3. What speed are you asking for NoSQL? development? Runtime? There is no acid with no SQL, if it is important for you, then why are you thinking about it? NoSQL means "Not Relative" Is Your Data Relational? If so, why are you considering NOQL?

     You can not decide on performance related issues by talking about technology and guessing. Its the only way to benchmark them and to get some real data for transactions that you really care about.

     Write the interface-based DAO, using the technique of each candidate, and to measure the actual results, how to decide on the extent to which technology is to be used.

     Which well do you know? If no one knows, do not use it. If you do not know JPA, do not use it. Spring JDBC template lets you write custom SQL with a transaction. If you already know the relational database and the spring, why would not you use it?