JPA/ORM vs JDBC for performance limited machines -
We are creating a small application that will be deployed on very limited machines. They only have 256 MB of RAM.
I would like to use JPA because it simplifies the code and removes the need for JDBC ResultText code. However, should the upper part of JPA be the factor of such small machines? I am currently thinking of using toplink, which comes in a 2.5 MB jar file.
We have only limited numbers, so JDBC code will not be very difficult. But JPA makes code very good.
Cheers.
The JPA / ORM display will always be equal to or equal to the JDBC in runtime because they are both based on JDBC .
As you noted, the development time of the big lift received from the JAPA / ORM is time.
I would like to use JPA because it simplifies the code and JDBC results remove the need for the code.
I'm not sure that I understand this statement. JPA will use a result set behind the scenario; You will not write it now, the mapping of objects from ResultSet is explained in XML or annotation.
If you are actually bound to memory, then you have to pass JPA and hand code to JDBC
In that case you can see Spring JDBC because it is very much for JDBC support Nice design that makes it very simple.
256 MB RAM? You will have a hard time using any third party libraries.
Comments
Post a Comment